search for: timer_sleep

I''ve now got 5 processes auto started. But I when I query the MiddleMan for their keys (in script/console), it doesn''t find them. Looking at the start script, it looks like it might be creating a new MiddleMan object for each autostart BackgrounDRb::MiddleMan.new.new_worker(:class => entry[''class''], Even changing it to

I''m having trouble getting backgroundrb up and running in a production environment. Here''s my backgroundrb.yml: --- port: "22222" timer_sleep: 60 load_rails: true environment: production host: XXX.XX.XXX.50 database_yml: config/database.yml acl: deny: all allow: localhost 127.0.0.1 XXX.XX.XXX.51 order: deny,allow I start BackgroundRB from XXX.XX.XXX.50 with script/backgroundrb/ start -d I can then telnet localhost 22222 and co...

...all, I just read Ezra''s article on BackgroundRb and decided to use it one of my projects. I installed the plugin into my rails project using script/plugin and then ran rake backgroundrb:setup to copy the yml scripts. Now my backgroundrb.yml looks like ======= --- port: "22222" timer_sleep: 60 load_rails: true environment: development host: localhost database_yml: config/database.yml acl: deny: all allow: localhost 127.0.0.1 order: deny,allow scheduled_task: :class: :tx_reaper_worker :worker_method: :do_work :trigger_args: :start: <%= Time.now %> :repeat_in...

...running rails - it slows things down a lot. I would like to keep running rails on my main server (server1) but move backgroundrb to a secondary server (server2). I looked through the source trying to figure out how to do this and I pieced together this configuration file: -- :port: 22222 :timer_sleep: 60 :pool_size: 15 :load_rails: true :rails_env: development :environment: development :host: localhost :uri: druby://localhost:22222/ :database_yml: config/database.yml :protocol: druby :acl: :deny: all :allow: localhost 127.0.0.1 server1 :order: deny,allow autostart: 1: job_key:...

example: :host: 192.168.1.101 :protocol: druby :worker_dir: lib/workers :rails_env: production :pool_size: 15 :load_rails: true :timer_sleep: 60 :acl: :deny: all :allow: localhost 192.168.1.* :order: deny allow I have this config file on 2 app servers running rails. The 2 servers are running behind a load balancer. I''m starting the backgroundrb server on the one server with the ip of 192.168.1.101. Each time I try to...

...2006 Sending due notes. The current time is Mon Aug 28 19:19:03 MDT 2006 Sending due notes. The current time is Mon Aug 28 19:20:03 MDT 2006 Sending due notes. The current time is Mon Aug 28 19:20:03 MDT 2006 Is there any way to fix that? Here is my configuration file: --- port: "22222" timer_sleep: 60 load_rails: true environment: development host: localhost database_yml: config/database.yml acl: deny: all allow: localhost 127.0.0.1 order: deny,allow autostart: 1: job_key: due_note_queuer1 class: due_note_queuer_worker Thanks, Martin

...run'' C:/Programme/ruby/lib/ruby/1.8/drb/drb.rb:1424:in `run'' C:/Programme/ruby/lib/ruby/1.8/drb/drb.rb:1344:in `initialize'' C:/Programme/ruby/lib/ruby/1.8/drb/drb.rb:1624:in `start_service'' script/backgroundrb/start:84 [2] background.yml port: "22222" timer_sleep: 60 load_rails: true environment: development host: localhost database_yml: config/database.yml acl: deny: all allow: localhost 127.0.0.1 order: deny,allow

i ran rake backgroundrb:setup and modified the default config/backgroundrb.yml file as: --- port: "22223" timer_sleep: 60 load_rails: true environment: production host: localhost database_yml: config/database.yml acl: deny: all allow: localhost 127.0.0.1 order: deny,allow and my database.yml production: adapter: mysql database: chip2_production username: xxxxx password: xxxxx socket: /var/lib/mys...

...n `run'' script/backgroundrb:29 I am at a loss to explain what is going on here. BackgrounDRb::VERSION reports I run version 0.2.1 of backgroundrb. I have version 1.2.1 of slave, and version 1.0.6 of daemons installed. My backgroundrb.yml file is the following: --- port: "22222" timer_sleep: 60 load_rails: true environment: production host: 127.0.0.1 database_yml: config/database.yml acl: deny: all allow: localhost 127.0.0.1 order: deny,allow Hopefully someone can help me get through this, because I am in the middle of deploying our first app, and it would suck to be delayed a...

Since MiddleMan is an uninitialized constant in a worker how do you create new workers inside a worker? Thank You, Ben Johnson E: bjohnson at contuitive.com O: 800-341-6826 M: 817-229-4258 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20060731/75a77fa6/attachment-0001.html

I''m trying to do the tutorial at http://www.infoq.com/articles/BackgrounDRb. A little more than half-way through it says "Upon instalation, the plugin writes a config file into RAILS_ROOT/config/backgroundrb.yml." It didn''t happen for me. I installed the plugin with: ruby script\plugin install svn:\\rubyforge.org//var/svn/backgroundrb It added a bunch of files,

...ed from an autostart configuration in backgroundrb.yml. Most of the time it seems to work just fine. If I say repeat_every 1.minute, it logs every minute. But somewhat often it double logs, indicating the do_work call was hit twice. I''ve tried this with a variety of repeat_every & timer_sleep values. I imagine the start_timer loop is somehow calling start_process on this same job more than once. Not sure how that could happen, from my read of the code. Anyone else seen this before? What evidence can I provide to help figure this out? Josh -- Joshua Warchol Code Poet, Zaadz Inc....

...18:14:31 (24026) socket_dir: /tmp/backgroundrb.24026 20070312-18:14:31 (24026) environment: development 20070312-18:14:31 (24026) host: localhost 20070312-18:14:31 (24026) acl: denyallallowlocalhost 127.0.0.1orderdeny ,allow 20070312-18:14:31 (24026) rails_env: development 20070312-18:14:31 (24026) timer_sleep: 60 20070312-18:14:31 (24026) port: 22222 20070312-18:14:31 (24026) pool_size: 5 20070312-18:14:31 (24028) Starting worker: BackgrounDRb::Worker::WorkerLogger backgroundrb_logger (backgroundrb_logger) () 20070312-18:14:31 (24028) Starting worker: BackgrounDRb::Worker::WorkerResults backgroundrb_res...

...:include => :comments) MiddleMan.cache_as(:post_cache, 300, @posts) #OR @posts = MiddleMan.cache_as :post_cache, 300 do Post.find(:all, :include => :comments) end #retrieve_cache @posts = MiddleMan.cache_get :post_cache do Post.find(:all, :include => :comments) end By default the timer_sleep is set to 60 seconds. This means that the timer will wakeup every 60 seconds and delete caches and worker that are past their time to live. You can change this in the config file if you want it to run faster or slower. All your worker classes should now inherit from BackgrounDRb::Rails so...

I have a very strange problem here. I do not get this. So any help is greatly appreciated. Basically I have a model that calls a method in the background process in the "after_save" method. Let''s call the model products. So what happens is this: 1. I create a new product. 2. Everything works and the product is saved with id 13. 3. A method is called in my background