similar to: Problem with workers starting workers

Hi Folks, I found this thread http://rubyforge.org/pipermail/backgroundrb-devel/2007-March/000790.html on this mailing list that describes pretty much the same behaviour that I experience as well. My problem is, that I have no chance for putting a "sleep 0" in an iteration because I have no Iteration. What I?m doing is executing a stored procedure in a sybase db that could take from

Hi, I have backgroundrb running to decouple the execution of massive business logic from an ActionWebservice request. The service is designed to take some configuration parameters and fire a lot of background workers to do the requested work. Due to performance reasons I want to limit the number of workers to a maximum number of 30. But when I start a configuration that requires for example

Hi Folks, I want to set up backgroundrb on my laptop to do some tests. But when I run "scripts/background start" I get this error: ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/daemonize.rb:160:in `setsid'': the setsid() function is unimplemented on this machine (NotImplementedError) from ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/daemonize.rb:160:in

This has been asked before, never well attended perhaps. Any thoughts on testing your workers? Current implementation is broken. An empty test case like this: require File.dirname(__FILE__) + ''/../test_helper'' require "#{RAILS_ROOT}/lib/workers/market_summary_worker" require "#{RAILS_ROOT}/vendor/plugins/backgroundrb/lib/backgroundrb.rb" require

I use backgroundrb for many long tasks in my system, but I''m having issues with one in particular. Two large tasks for me are importing people and updating companies. def import_contacts(args = nil) thread_pool.defer(args) do |job_id| begin job = ImportJob.find(job_id) job.process_job rescue => err logger.error "MscWorker#import_contacts

Hi folks, I''ve got some BackgroundRB workers to handle a long running task (triggered by a user) that work very well on my staging server, and I just wanted to check to see if anyone had any advice before I put it into production. When I start the worker (which performs an import), I write a record to my database for each import. The record gets updated by the worker to

Hi gang, Thanks to other help I''ve gotten on this list, I''ve got backgroundrb up and running using postgres alongside my rails app. I''ve designed the system to have several eternally-running workers that periodically poll the database to see if there''s any work for them to do, and set things up in the config file to make them restart quickly if any of them

Hello, We are working on a centralized report generating project, which calls for data processing on different servers and then centralizes the reports into a single project. What we would like to do is have a Monitor BackgrounDRb worker call another BackgrounDRb worker to process data on a different server, and then have our Monitor Worker collect the data and then store it according to our

I''m just getting started with backgroundRb and have run into a bit of problem... I want to have my controller launch one worker which in turn launches multiple child workers. When trying to use MiddleMan.new_worker in the parent worker I get a "recycled object" error. Is it not possible to launch workers from within another worker? TIA, for any help. - Jordan Glasner

Hello, I''m using the scheduler to create several reusable workers of the same type, .e.g., RSSWorker, so I can avoid the overhead of initializing new processes (as suggested by Ezra to my previous question). Creating new workers through the external yaml seems pretty straightforward, but my question is is there a way to call these workers without using the job key? Currently, to use

Hi all, I need some help with this setup I am trying to get working with BackgrounDRb: An autostarted "dispatcher" worker runs every minute and polls some table for jobs that need to be run at that time. For each job found, the "dispatcher" spawns a "runner" worker that runs the job. So in my "dispatcher" worker, I have some code like this:

I had a worker scheduled to run every minute with backgroundrb_schedules.yml: ebay_runner: :class: :ebay_auction_worker :job_key: :ebay_auction_runner :trigger_type: :cron_trigger :trigger_args: 0 * * * * * * This worker posts an auction to eBay from a queue of auctions every minute. I was having a problem where the worker would run ok the first time, but never any subsequent minutes

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

Hi, I''m using backgroundrb but I have 2 problems with it. First is when I launch a thread Toto from the do_work method. Toto can''t access to a class variable defined before... (undefined method `+'' for nil:NilClass) I suspect that thread is launched when backgroundrb start but the worker not .. My code is : class MonWorker < BackgrounDRb::Worker::RailsBase

I''m having some issues with Workers dying after a period of several hours. Each worker runs a loop that asks Amazon SQS for work to do. If there is a message in the queue the work is completed (image processing, etc...); if there is no message the worker will sleep for X seconds (sleep 10, etc...). I''ve noticed that the workers will frequently exhibit two negative

Hello all, I just looked through the list and didn''t find a good answer to this.. so posting away. I have some backgorunDRB workers that are all working nicely. In fact, I have no problem right now. But when i was doing the coding, I found a need occasionally to fire up the debugger and have a look at what was going on inside, but found no way to do this directly. Is there a way to

Hi, I''m using backgroundrb 0.2.1 and having problem with worker processes staying around when the rails application does not explicitly delete them. Is there a way to automatically delete the worker processes when it has completed the job? Also does killing the process manually (using kill command) harm the backgroundrb server? I have some occasions where the backgroundrb server just

Hi, it would be nice to be able to specify workers as singletons. By this I mean that every call to the new_worker method returns the same instance of said worker. This can be done transparently either by adding a new argument to new_worker (something like :singleton => true) or adding a new method, like I did in my installation of BackgrounDrb: def get_worker_by_class(klass)

I''ve got some workers that I want to have running all the time. Right now I''m just launching them manually, by requesting a special page in my rails app that includes lines like: MiddleMan.new_worker(:class=> :receiver, :job_key=>:r, :args=>{:sleep_time=>10}) This strikes me as a really weak way to fire up my workers. I basically want to automate things so

Hi Folks, it?s quite a while that I used BackgrounDRb and I was hoping that I get the chance on working with it again, as I read so many promising things here in the list! When I last worked with it (Rel. 0.21) there was no way of running it under Windows. Is this restriction still valid? I hope not, as I desperately need to get it working with InstantRails in a Windows environment for some new