similar to: Bug in meta_worker.rb

I''ve been using backgroundrb for... about an hour now. I must say, I''m impressed. But I''m a bit stumped on where to find the "official" documentation. There''s an API online at backgroundrb.rubyforge.org, but I don''t see the methods available for MiddleMan, etc. Right now, I''m trying to figure out how to get a list of all

After some initial stumblings, I think I''ve got the hang of backgroundrb. It''s great! I''d been thinking for many many months how cool something like this would be! I''m trying to make a "job queue". That is, a pool of worker threads monitor a queue. When a job appears, one of the workers grabs it and executes the task. When complete, the worker

I''m running a fresh checkout of release 1.0.1 ... It''s now 11:32 am local time on January 31. I''ve configured a single worker for a test. If I use the following schedule in my background.yaml file: :schedules: :debugger_worker: :ping: :trigger_args: 0 35 11 * * * * Backgroundrb starts up without error. If I make the following

Hi, I have a relatively simple Worker: (I added the line numbers to the email, they are not in the worker) ##################################################################################### class ImagetestWorker < BackgrounDRb::MetaWorker set_worker_name :imagetest_worker def create(args = nil) end def save_image(args) @newbook = Book.new @newbook.comment =

Trying to use backgroundrb to process and insert a large list of bulk records, but when I try to use it with the batched_sql_fu plugin installed in vendor/plugins, I get the following error: ---SNIP--- /Users/jdonalds/Sites/3dial_ads/config/../vendor/plugins/ batched_sql_fu/lib/batched_sql_fu/active_record.rb:22:in `alias_insert_sql_to_batched_version!'': undefined method

Hi, I was trying to schedule a worker to run during the midnight hour like this: :schedules: :collector: :process_something: :trigger_args: 30 * 0 * * 2,3,4,5,6 When I try to start backgroundrb, the "collector" worker failed to start up and I find this in backgroundrb_server.log: /home/mengkuan/apps/testrailsapp/current/vendor/plugins/backgroundrb/

Hi, I am playing around with backgroundrb 1.0.3. I have the following backgroundrb.yml, --- :backgroundrb: :port: 11006 :ip: 0.0.0.0 :schedules: :task_worker: :run: :trigger_args: */10 * * * * * My task worker is just, class TaskWorker < BackgrounDRb:MetaWorker set_worker_name :task_worker def run logger.info "begin" sleep 60 logger.info

Hi everyone, I noticed that script/backgroudrb requires config/environment which causes the backgroundrb server as well as the log worker to ''bloat'' to 35MB each. I am kind of sensitive to memory issues, so I patched the code and essentially moved the require of environment from script/backgroundrb to the meta_worker. Everything seems good and now both backgroundrb server and

Hi, I''ve been using bdrb for a while and just recently found the need to use the ask_status/register_status functionality of my worker. This is the error I get whenever the register_status method is encountered: ...lib/workers/session_worker.rb:10:in `create'': undefined method `register_status'' for #<SessionWorker:0xb6e7d52c> (NoMethodError) from

Hello, First off, nice improvements hemant! Thanks for all the hard work. I just whipped up a new worker for a scheduled job that sends digest emails. Very smooth. However, moving some of my old backgroundrb into new backgroundrb isn''t going quite as smoothly. I have a import worker that takes a number of parameters and then is started dynamically. Here''s the a

Hi, New BackgrounDrb user struggling for a couple of days to get things up an going. System: Ruby 1.8.6 Packet 0.1.5 chronic 0.2.3 BackgrounDrb 1.0.3 (downloaded 4/02/08 and 4/03/08) I installed the packet and chronic gems as per instructions. I used git to download BDrb as per instructions and ran the rake setup script. When I run script/backgroundrb from my rails app main directory, I get

I''ve only been working with backgroundrb a few days so I don''t know much of the procedures involved with its development.... But I came across what I consider a glitch in the latest GIT version of the source. The file server/lib/metaworker.rb at line 247 result = "dummy_result" unless result should be changed to:: result = "dummy_result" if result.nil?

I get this error periodically in backgroundrb.log, but only on my production box (the one running ruby 1.8.5) - my dev box doesn''t get this error. As far as I can tell, everything is working ok, despite the error (I don''t really know how to determine if the jobs are getting threaded successfully, but they are running, that I am sure of). Here''s the dump: no

Hi, I am using the latest checkout from backgroundrb release 1.0.1. I have a worker called status_checker that periodically (every minute) checks the status of certain hosts over the network. It works fine at the beginning but after a while the worker will mysteriously disappear and stop working. I have other workers running but they do not disappear like this worker does. These are

Hi there I have recently upgraded to v1.0.1 and I''ve noticed an issue which I don''t believe was present in the 0.2 release. In my worker class I am logging errors as follows: logger.error "the error message" However, this now causes an exception to be thrown in the new version: undefined method `error'' for

I tried to upgrade my existing application to RC2 last night. Like many, I use this mostly for running scheduled tasks. For the moment, I''ve abandoned the effort, but am looking forward to being able to use this. Feedback below: First, the reason I was looking forward to this upgrade was to use the threaded scheduler. I have an application with long-running tasks. I found that

I figured out that in the backgroundrb.yml, I had the old setting of making the database RAILS_ENV. It wasn''t a valid variable in backgroundrb 0.2.1, and it wasn''t reporting an error, so I had no idea. Once I changed it to ''development'' or ''production'', it started working. I found that if a worker has an error, it usually logs the error

Hi, I''m using backgroundrb 0.2.1 in a production environment and for most parts I''m very happy. We are using it to do some heavy video editing on the server side and it works great except that under, what seems heavy load the below problem happens intermittently. The problem has only happened 5 times out of over 500 runs by our backgroundrb worker. This is the code in our

In my app, I store the job key when a worker is fired off and then check back in periodically to see how its doing. The workers delete themselves when they''re done. I would expect when I try to get a worker that has been deleted, I would get nil or a proper exception, but instead I get: >> MiddleMan.worker(''foobar'') NoMethodError: undefined method

Hi Folks, I am glad to announce a 1.0.1 release of BackgrounDRb library. It has numerous fixes and some nice feature updates, so please upgrade. Code: http://svn.devjavu.com/backgroundrb/tags/release-1.0.1/ Updates and Fixes: * Fixed issue with Mysql Lost connections * Message debugging can be disabled now with ''debug_log'' option in configuration file( :debug_log: false)