search for: start_reactor

...from /usr/lib/ruby/gems/1.8/gems/packet-0.1.6/lib/packet/packet_core.rb:163:in `each'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.6/lib/packet/packet_core.rb:163:in `handle_write_event'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.6/lib/packet/packet_core.rb:135:in `start_reactor'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.6/lib/packet/packet_core.rb:126:in `loop'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.6/lib/packet/packet_core.rb:126:in `start_reactor'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.6/lib/packet/packet_maste...

.../master_worker.rb:33:in `receive_data'' /vendor/plugins/backgroundrb/framework/packet/core.rb:199:in `read_external_socket'' /vendor/plugins/backgroundrb/framework/packet/core.rb:191:in `handle_external_messages'' /vendor/plugins/backgroundrb/framework/packet/core.rb:160:in `start_reactor'' /vendor/plugins/backgroundrb/framework/packet/core.rb:156:in `each'' /vendor/plugins/backgroundrb/framework/packet/core.rb:156:in `start_reactor'' /vendor/plugins/backgroundrb/framework/packet/core.rb:147:in `loop'' /vendor/plugins/backgroundrb/framework/packet/cor...

...ib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:174:in `each'' from /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:174:in `handle_read_event'' from /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:130:in `start_reactor'' from /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:124:in `loop'' from /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:124:in `start_reactor'' from /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.5/li...

...ckgroundrb/framework/worker.rb:52:in `receive_internal_data'' /var/www/apps/rpg/releases/20071224050255/vendor/plugins/backgroundrb/framework/worker.rb:48:in `handle_internal_messages'' /var/www/apps/rpg/releases/20071224050255/vendor/plugins/backgroundrb/framework/core.rb:158:in `start_reactor'' /var/www/apps/rpg/releases/20071224050255/vendor/plugins/backgroundrb/framework/core.rb:156:in `each'' /var/www/apps/rpg/releases/20071224050255/vendor/plugins/backgroundrb/framework/core.rb:156:in `start_reactor'' /var/www/apps/rpg/releases/20071224050255/vendor/plugin...

...s/backgroundrb/lib/../framework/nbio.rb:23:in `read_data'': Packet::DisconnectError (Packet::DisconnectError) from RAILS_HOME/vendor/plugins/backgroundrb/framework/worker.rb:47:in `handle_internal_messages'' from RAILS_HOME/vendor/plugins/backgroundrb/framework/core.rb:158:in `start_reactor'' from RAILS_HOME/vendor/plugins/backgroundrb/framework/core.rb:156:in `each'' from RAILS_HOME/vendor/plugins/backgroundrb/framework/core.rb:156:in `start_reactor'' from RAILS_HOME/vendor/plugins/backgroundrb/framework/core.rb:147:in `loop'' from RAILS_HO...

...from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:174:in `each'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:174:in `handle_read_event'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:130:in `start_reactor'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:124:in `loop'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:124:in `start_reactor'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_ma...

.../framework/bin_parser.rb:29:in `extract'' backgroundrb/server/master_worker.rb:12:in `receive_data'' backgroundrb/framework/core.rb:191:in `read_external_socket'' backgroundrb/framework/core.rb:183:in `handle_external_messages'' backgroundrb/framework/core.rb:156:in `start_reactor'' backgroundrb/framework/core.rb:152:in `each'' backgroundrb/framework/core.rb:152:in `start_reactor'' backgroundrb/framework/core.rb:144:in `loop'' backgroundrb/framework/core.rb:144:in `start_reactor'' backgroundrb/framework/packet_master.rb:20:in `run'...

Hi, Is it possible to start a worker with job_key and then ask_status of that specific worker with the job_key? MiddleMan.ask_work(:worker => :auth_worker, :job_key=>''1'', :worker_method => :auth) and then MiddleMan.ask_status(:worker => :auth_worker, :job_key=>''1'') >From my testing of the new backgroundrb, asking status using job key

I tried to upgrade my existing application to RC2 last night. Like many, I use this mostly for running scheduled tasks. For the moment, I''ve abandoned the effort, but am looking forward to being able to use this. Feedback below: First, the reason I was looking forward to this upgrade was to use the threaded scheduler. I have an application with long-running tasks. I found that

...9;' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/ packet_core.rb:174:in `each'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/ packet_core.rb:174:in `handle_read_event'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/ packet_core.rb:130:in `start_reactor'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/ packet_core.rb:124:in `loop'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/ packet_core.rb:124:in `start_reactor'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/ packet_master.rb:21:in `...

...r_proxy.rb:21:in `initialize'' from /opt/ruby-enterprise-1.8.6-20081215/lib/ruby/gems/1.8/ gems/packet-0.1.14/lib/packet/packet_core.rb:141:in `call'' from /opt/ruby-enterprise-1.8.6-20081215/lib/ruby/gems/1.8/ gems/packet-0.1.14/lib/packet/packet_core.rb:141:in `start_reactor'' from /opt/ruby-enterprise-1.8.6-20081215/lib/ruby/gems/1.8/ gems/packet-0.1.14/lib/packet/packet_core.rb:139:in `loop'' from /opt/ruby-enterprise-1.8.6-20081215/lib/ruby/gems/1.8/ gems/packet-0.1.14/lib/packet/packet_core.rb:139:in `start_reactor''...

...'' /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.10/lib/packet/packet_core.rb:190:in `each'' /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.10/lib/packet/packet_core.rb:190:in `handle_read_event'' /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.10/lib/packet/packet_core.rb:144:in `start_reactor'' /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.10/lib/packet/packet_core.rb:137:in `loop'' /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.10/lib/packet/packet_core.rb:137:in `start_reactor'' /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.10/lib/packet/packet_master.rb:21:in `run...

...9;' /usr/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/ packet_core.rb:174:in `each'' /usr/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/ packet_core.rb:174:in `handle_read_event'' /usr/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/ packet_core.rb:130:in `start_reactor'' /usr/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/ packet_core.rb:124:in `loop'' /usr/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/ packet_core.rb:124:in `start_reactor'' /usr/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/ packet_master.rb:21:in `...

I''ve been using backgroundrb for... about an hour now. I must say, I''m impressed. But I''m a bit stumped on where to find the "official" documentation. There''s an API online at backgroundrb.rubyforge.org, but I don''t see the methods available for MiddleMan, etc. Right now, I''m trying to figure out how to get a list of all

I lost my "connection lost" error.. but now I''ve got a "Mysql::Error: MySQL server has gone away" error.. It comes from: /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.6/lib/active_record/connection_adapters/abstract_adapter.rb:128:in ''log''. I''m not sure if Rails / BackgroundRb uses it .. but i''ve got the mysql (2.7) gem

...20080115103838/vendor/plugins/ backgroundrb/server/meta_worker.rb:329:in `check_for _timer_events'': undefined method `info'' for nil:NilClass (NoMethodError) from /home/webcon/apps/webconsole/releases/20080115103838/ vendor/plugins/backgroundrb/framework/core.rb:148:in ` start_reactor'' from /home/webcon/apps/webconsole/releases/20080115103838/ vendor/plugins/backgroundrb/framework/core.rb:147:in ` loop'' from /home/webcon/apps/webconsole/releases/20080115103838/ vendor/plugins/backgroundrb/framework/core.rb:147:in ` start_reactor''...

...ting the DB query to return no more than 255 records and then all is fine. No problems at all. But over that, I see this issue. Repeatedly. Here''s what I found in my log/backgroundrb_11007_debug.log file. ========= /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:124:in `start_reactor'' /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_master.rb:21:in `run'' /home/raghus/public_html/ feedflix.com/ff/vendor/plugins/backgroundrb/server/lib/master_worker.rb:166:in`initialize'' ./script/backgroundrb:42:in `new'' ./script/backgroundrb:42 {:typ...

...nk/vendor/plugins/backgroundrb/server/lib/meta_worker.rb:325:in `each'' from /Users/pkmiec/src/propertyadmin/trunk/vendor/plugins/backgroundrb/server/lib/meta_worker.rb:325:in `check_for_timer_events'' from /Library/Ruby/Gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:125:in `start_reactor'' from /Library/Ruby/Gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:124:in `loop'' ... 6 levels... from /Library/Ruby/Gems/1.8/gems/packet-0.1.5/lib/packet/packet_master.rb:20:in `run'' from /Users/pkmiec/src/propertyadmin/trunk/vendor/plugins/backgroundrb/server/...

Hi, A pre-release version of backgroundrb is available now from svn. Download it from here: http://svn.devjavu.com/backgroundrb/branches/version099/ Since this release marks significant migration from existing practices, i intend to keep trunk untouched for a while. There are no install scripts, but you should copy "backgroundrb" file from script directory of plugin to script

Hey all, Been reading through all the old posts (and the docs) to familiarize myself but I still feel a bit lost. I''m on trunk and am having a bit of a hard time knowing where to start with the particular I''m trying to solve. So far, I''ve downloaded backgroundrb, done the basic rails setup, created my worker and started it using `script/backgroundrb start`.