chuckremes / rzmq_brokers Goto Github PK

after timing out on connecting to the broker, I get this message:

warn|20120121-13:28:00.865350 EST|RzmqBrokers::Worker::Handler, Worker [db-lookup] exceeded broker tries; reconnecting!
error|20120121-13:28:00.865778 EST|RzmqBrokers::Worker::Handler Worker could not cancel heartbeat timer! [delay [3000], periodical? [true], fire_time [2012-01-21 13:28:00 +1100] fire_delay_ms [-6]] proc [#Proc:0x0000010186df88@/Users/mwotton/projects/rzmq_brokers/lib/rzmq_brokers/worker/handler.rb:144]. Confirm that this object is only accessed by the reactor thread that created it. [worker-reactor] vs []
error|20120121-13:28:00.866139 EST|RzmqBrokers::Worker::Handler Worker could not cancel broker timer! [delay [9000], periodical? [true], fire_time [2012-01-21 13:28:09 +1100] fire_delay_ms [8999]] proc [#Proc:0x0000010186c9d0@/Users/mwotton/projects/rzmq_brokers/lib/rzmq_brokers/worker/handler.rb:160]. Confirm that this object is only accessed by the reactor thread that created it. [worker-reactor] vs []

and the process takes 99% cpu thereafter.

I'm using your db_lookup.rb sample code, just deleting the client and broker setup. Should the code be running inside the reactor?

./lib/rzmq_brokers/consensus/broker/service.rb: def send_client_reply_failure
./lib/rzmq_brokers/consensus/broker/service.rb: @handler.send_client_reply_failure(@return_address, @message)
./lib/rzmq_brokers/majordomo/broker/service.rb: @handler.send_client_reply_failure(@envelope_msgs, @reply)
./lib/rzmq_brokers/majordomo/broker/service.rb: @handler.send_client_reply_failure(@envelope_msgs, nil, frames)
./lib/rzmq_brokers/broker/handler.rb: def send_client_reply_failure(return_address, message, frames=[])

I added "fframe=[]" to the last line - it was being called with only two arguments. just a hack to stop it from dying, not sure what the real solution is.

I tried using the majordomo broker C code from the guide, and it complained about invalid messages. Does the ruby broker speak a different protocol? I noticed PROTOCOL_VERSION = "Mdp200" in message.rb, but couldn't find anything more about that protocol version.

any chance of pushing to rubygems as a legit gem that can be relied upon by other published gems?