Can you post your worker code? There is a known problem with OSX where a newly spawned worker becomes usable only after fraction of second.
Although it works okay on Linux. On Wed, 2008-09-10 at 10:00 -0400, Sam Hendley wrote: > Hello all, I have been researching background processing options and I > think BackgroundDRb is a good fit for our project. > > > > I set up a test project to play around and prototype the behavior I > want but I ran into the same problem as Reynard. I created a skeleton > worker using the generator and I am trying to call a test function on > the worker. (basically following the tutorial) > > > > Here’s the code I’m trying to run: > > > > >> MiddleMan.new_worker(:worker => :upload_worker, :worker_key > => :test_key) > > => “work” > > >> MiddleMan.worker(:upload_worker, :test_key).upload() > > => nil > > > > And heres what I see in the logs: > > Invalid worker with name upload_worker_test_work and key test_work > > > /usr/lib/ruby/gems/1.8/gems/packet-0.1.13/lib/packet/packet_connection.rb:52:in > `ask_worker' > > > /home/sam/bdb_test/vendor/plugins/backgroundrb/server/lib/master_worker.rb:103:in > `async_method_invoke' > > > /home/sam/bdb_test/vendor/plugins/backgroundrb/server/lib/master_worker.rb:37:in > `receive_data' > > /usr/lib/ruby/gems/1.8/gems/packet-0.1.13/lib/packet/packet_parser.rb:44:in > `extract' > > /usr/lib/ruby/gems/1.8/gems/packet-0.1.13/lib/packet/packet_parser.rb:26:in > `loop' > > /usr/lib/ruby/gems/1.8/gems/packet-0.1.13/lib/packet/packet_parser.rb:26:in > `extract' > > > /home/sam/bdb_test/vendor/plugins/backgroundrb/server/lib/master_worker.rb:32:in > `receive_data' > > /usr/lib/ruby/gems/1.8/gems/packet-0.1.13/lib/packet/packet_core.rb:232:in > `read_external_socket' > > /usr/lib/ruby/gems/1.8/gems/packet-0.1.13/lib/packet/packet_core.rb:222:in > `handle_external_messages' > > /usr/lib/ruby/gems/1.8/gems/packet-0.1.13/lib/packet/packet_core.rb:196:in > `handle_read_event' > > /usr/lib/ruby/gems/1.8/gems/packet-0.1.13/lib/packet/packet_core.rb:192:in > `each' > > /usr/lib/ruby/gems/1.8/gems/packet-0.1.13/lib/packet/packet_core.rb:192:in > `handle_read_event' > > /usr/lib/ruby/gems/1.8/gems/packet-0.1.13/lib/packet/packet_core.rb:146:in > `start_reactor' > > /usr/lib/ruby/gems/1.8/gems/packet-0.1.13/lib/packet/packet_core.rb:139:in > `loop' > > /usr/lib/ruby/gems/1.8/gems/packet-0.1.13/lib/packet/packet_core.rb:139:in > `start_reactor' > > /usr/lib/ruby/gems/1.8/gems/packet-0.1.13/lib/packet/packet_master.rb:21:in > `run' > > > /home/sam/bdb_test/vendor/plugins/backgroundrb/server/lib/master_proxy.rb:14:in > `initialize' > > script/backgroundrb:46:in `new' > > script/backgroundrb:46 > > > > Reynard did you ever solve this problem? It must be something basic I > am missing can anyone point me in the right direction? > > > > Thanks > > Sam Hendley > > > _______________________________________________ > Backgroundrb-devel mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/backgroundrb-devel _______________________________________________ Backgroundrb-devel mailing list [email protected] http://rubyforge.org/mailman/listinfo/backgroundrb-devel
