chuckremes/rzmq_brokers — Issue #3: when worker is run alone, process spins
Author: mwotton
Created: 2012-01-21 02:30:10+00:00
State: open

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 [#]. 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 [#]. 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?