similar to: BackgrounDRb background task runner and Application Wide Context Store

Hey all, I need to launce a rather lengthy process from a small Rails application. It''s the sort of thing (sending out an email newsletter) that would need to be launched from a browser window, but the browser doesn''t need to stick around to see it through. I played around with Thread.new, but I think, based on limited testing, that the threads need to complete before the view

Friends- There is a new release of BackgrounDRb. This time it is a full fledged rails plugin with generators and rake tasks thanks to Saimon Moore. Thanks Saimon! You can read all about it here on my blog: http://brainspl.at/articles/2006/05/25/backgroundrb-new-release The newest feature besides the much cleaner way to install and control the drb server is caching. You can now use

Folks- I just commited another revision of the plugin. Nothing huge in this update but some extra features. Acl lists are now configurable in the config file. So you will want to blow away and recreate your config file again. Thanks to Georg Friedrich for this. And I applied Gunter Ladwig''s patch for singleton worker classes. These are workers that only have one instance of

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 am using BackgrounDRb to resize images after they are accepted into our system. However, it has become clear that this creates a memory leak. I''m not sure exactly where the leak exists, but I don''t think it''s in my own code as it is presently being used in production and has resized thousands of images without a leak occurring, thanks to calling GC.start

Hey there bdrb''ers! I have been so very busy with http://engineyard.com that I have not had time to complete the new release of backgroundrb. But I have done substantial work towards it. It is basically an entirely new beast with a complete rethinking of how it works. I have put up a zip file of the new code base in the hopes that some folks will be able to start playing with

Howdy Folks- I''m happy to announce a new release of BackgrounDRb! I have added quite a few new features and included some nice patches from folks on the list. $ script/plugin install svn://rubyforge.org//var/svn/backgroundrb All of the code now stays within the plugin and the start and stop scripts are now just stubs. This makes it easier to tweak or figure out how it works.

Hi. I thought that BackgrounDrb was the perfect solution for my long running report production tasks. But I can''t seem to get anything useful back out of it. I set up a simple test worker that just does class TestWorker < BackgrounDRb::Rails attr_reader :pupil def do_work(args) @progress=0 @pupil=Pupil.find(3) sleep rand*10 @progress=100 end when I try to

Can''t believe I can''t see the problem here, but after a few hours bashing my head on a brick wall, going to risk looking stupid by seeing if anyone can point out my idiocy (that''s the worst thing about coding on your own). Trying to get BackgrounDRb to take over the scraping task which is currently being done in a Rails controller. That''s not the problem at

Hi all I''m experiencing something strange with a :job_key, it took me a very long time to find out a worker wasn''t doing it''s job because of the name of my job_key. The first one I tried was :make_kohier, and with that name (and lot''s of other ones) I can''t get the worker to work. I do get my key in return, but the job doesn''t start

Hi Ezra, Thanks for the great work on BackgrounDRb. I have come across a couple of problems. 1. I wanted to define a simple class in the worker file to wrap up and pass back some data to my controller. It seems that if I create the class either inside or outside of my worker class (in the same file) it gets wrapper by a DRb::DRbUknown object and therefore cannot be accessed from my controller.

In response to my Rails Weenie post today[1], someone mentioned that I try BackgrounDRb to help take the strain off my application. 1: http://rails.techno-weenie.net/question/2006/7/13/nested-loops- best-way-to-send-messages-to-blog-subscribers I''ve just tried to install and use BackgrounDRb with my app, but I''m afraid that I''m not too versed in running processes

got a wierd problem maybe someone can help with. whenever i try to pass an array or AR objects to my worker, i end up with a DRb object in the worker...here''s an example class SearchWorker < BackgrounDRb::Rails attr_reader :resources def do_work(resources) logger.info resources.inspect end end class SearchController < ApplicationController def start_search

Hey Guys, In the readme for Backgroundrb it says that windows support has been depcreated for this version, but then it goes on to mention how to use it in Windows. So I''m not sure if it should be running on windows or not, so I''ll ask anyway. Also, I''m new to ruby and I''m also new to server administration, so I apologize if my questions are pretty

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 Im uploading a file to my rails app, i''s usually a large file, 5-50mb. Once the file has been uploaded it must be parsed and processed, this can take a very long time, 1-20mins. The problem is that most of the time my browser timeouts. Im not really sure how to solve it. One idea is that i have a script run constantly on the server that checks for uploaded files in a

Hi All, I''m using Backgroundrb as a general purpose long-running-task back-end (upload processing, email sending, etc), and it''s been a great solution. However I''ve recently run into some some intermittent connection issues that have me baffled. I''m running on apache2/fcgid and the problem occurs in both devlopment and production mode. The problem seems to

I just had an interesting issue on a production system that has been running nicely for about a year. There were approximately 10,000 backgroundrb temp files in the /tmp directory. It looks like backgroundrb wasn''t cleaning them up. I noticed it with the following error: DRb::DRbConnError: drbunix:///tmp/backgroundrb.20015/ backgroundrb_logger_0_0.101544829808665 -

I have a job that I am starting from a Rails controller in production mode using MiddleMan: MiddleMan.new_worker(:class => :import_ccg_category_worker, :args => { :category_id => @category.id, :remote_category_id => params[:remote_category_id], :description => "Importing CCG products for #{@ category.name}" }) Both of the category ID variables are just basic integers. I

Hi, First off, thanks Ezra for showing the way with BackgrounDrb. It''s a real godsend. I wanted to add a bit of job control to the system so that I could cancel DRB processes and so on. I thought I''d share how I did it in case anyone should find it useful or have feedback. I wanted to be able to put checkpoints into the drb job so that I could let the job do whatever needs to