search for: job_ctrl

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

...system. (this is observable with a netstat |grep mysql) This can be workaround by setting ActiveRecord::Base.allow_concurrency to false (do not see the risks but there are some probably) or by manually closing the connections in worker before termination the tread (in this case you have to use job_ctrl to avoid thread to be killed before having closed the connections) Cronned restart of backgroundrb also fix this :) Anyway maybe the problem is in the design of Backgroundrb itself, that should use a pool of thread and not create as many thread as there are works, in this case the pool of thre...

...otherwise instructed to be killed. I''m running an audio & video converter process, and I want to handle the case where the conversion takes too long -- setting a flag to "Failed", for example. I don''t want the job to just get killed... I saw something about @job_ctrl in the comments, but nowhere did I see it actually _used_. Is this implemented by DRb? -Matt Pennig -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20060810/91546e8c/attachment.html

Hello all, I''ve come up w/ a worker class that manages queued jobs using a fixed number of child workers. Well, that''s not quite true -- a new worker is spawned for each job, but you set the total number that may exist at once. There are three components: 1) queue_worker.rb: The singleton worker that manages the child workers. You probably want to auto start this. Make sure you