similar to: BackgrounDRb not working properly with files ?

Hey. I have a very annoying problem, and was wondering what is wrong. Suppose I have backgroundrb running, and then I have an action in some controller. In the action I define a worker. When leaving the action, suddenly the connection to backgroundrb is lost: DRb URI: druby://localhost:22222 Pid: 3976 Autostart... done druby://localhost:42531 - #<Errno::EBADF: Bad file descriptor -

Looks like my first question a couple of days ago wasn?t very clever asked, at least very sucessfull.... So, anyway...i will try it again: I have to prefix that I am far away from fully understanding the overall concept yet, and there?s no way to get some hints in the www so far, at least my resaerches dont lead to any helpfull stuff. image_controller.rb: def create MiddleMan.new_worker

Hi, First, thanks for the plugin. Sorry if this is not strictly a backgroundrb issue but I thought others on this list might have come across this problem. I''m trying to run the test that comes via the worker generator. The test works fine when running ''rake test_functional'', but when the tests are run by autotest I get "uninitialized constant BackgrounDRb"

Hi there, I''ve been experimenting with implementing BackgroundDRb in my rails app but am running into some problems. The primary problem I''m getting is in cleaning up worker threads, or getting any kind of response out of worker threads. If try using the response function/hash in my Worker the worker will not execute reporting that response is an unknown variable or function.

Hi there, I''ve been digging around trying to find some information (mostly examples) on how one would handle a progress bar upload using BackgrounDRb and File Column. I did read http://backgroundrb.rubyforge.org/ and Ezra''s blog of course, but I still have a few questions. I made a simple upload form (as a test) that is submitted to the "upload_song" action. def

this: Index: script/backgroundrb/lib/backgroundrb.rb =================================================================== --- script/backgroundrb/lib/backgroundrb.rb (revision 16) +++ script/backgroundrb/lib/backgroundrb.rb (working copy) @@ -29,7 +29,11 @@ # the log via @logger def initialize(args) @logger = BACKGROUNDRB_LOGGER - Thread.new { do_work(args) } +

I''m digging into BackgrounDRb and having some problems testing a worker class. The following line in my test (created from script/generate worker Test) throws an error: worker = TestWorker.new(:test_string => "testing...") Error: /activesupport/lib/active_support/dependencies.rb:123:in `const_missing'': uninitialized constant BackgrounDRb (NameError) from

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

Hi, I''m having a problem where connections started through BackgrounDRb::MiddleManDRbObject.init are not stopped, resulting in an ever growing established connections between my Mongrels and remote backgroundrbs I added DRb.stop_service to my code executed after requests that init MiddleManDRbObjects but that does not help. Any ideas? Thanks, Robert Bjarnason

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

I''m just getting started wtih backgroundrb, and unfortunately hit a snag right away... I''m running the latest releases of rails, backgroundrb, slave and daemons. I created a simple worker class, using the generator, which currently does nothing but print the arguments that are passed to do_work. I''m running backgroundrb using ''./script/backgroundrb

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.

I''m using backgroundrb to periodically download a large file via ftp from a remote location and then import it into the database. To perform the import, I was using the following: ActiveRecord::Base.connection.execute(%{load data infile ...;}) although on a file with 2.5 million records, this can take 5 minutes, which seems to tie up my rails application while this executes (even

I installed BackgrounDRB as instructed: script/plugin install svn://rubyforge.org//var/svn/backgroundrb rake backgroundrb:setup I started it with: rake backgroundrb:start In a model I make the call: MiddleMan.new_worker :class => :rss_worker In /lib/workers I have file rss_worker.rb, which contains the class: Class RssWorker < BackgrounDRb::Rails def do_work(args) ... end end

I''ve been having a terrible time with the backgroundrb scheduler. The issues I''m having is that the scheduled actions aren''t ran at all and if they do, the process stays around forever. I''m using the backgroundrb as a nightly cron to run some accounting operations. questions: 1. How can I have the process destroyed after the worker completes? 2. Any idea on

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, Ok, As i promised.. I am working on new version of BackgrounDRB, which is getting close and will be out soon. I need some feedback from you guys. So, please reply back. The code has changed significantly and its no longer using DRB. But I will keep the name BackgroundRb. Ok, in new API, a worker looks like this: require "net/smtp" require "guid" class NewsletterWorker

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

Hi there, I''m trying to create a worker to do some asynchronous web client work and update the data model with its results. It seems, however, that every call I make to an ActiveRecord subclass causes the whole thing to block. At least I think it''s blocked. Right now I''m just using debug log output. Is there a decent way to debug/test workers I can try? Is there any

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