similar to: Scheduled Workers

We have a fairly expensive task that we''d rather not schedule too many instances of in parallel. Couldn''t get pool_size to limit the amount of workers, and I figure that''s hardly optimal anyway, so would like to have the work queued up for a single named worker instead, running as soon as possible. Using MiddleMan.schedule_worker() with :job_key does start off a

hi I am implementing delayed_job in my rails app. *my code is:* file name is: my_worker.rb require "delayed_job" require "rubygems" class MyClass def perform while true do puts "I am in My class!!!" sleep 2 end end end Delayed::Job.enqueue( MyClass.new ) #m.perform when i am executing this(ruby my_worker.rb ) file it gives me error

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, i''m trying desperately to schedule some worker methods within rails 2.0.2. The problem is, both methods don''t even get called by BackgrounDRb. my background.yml: > --- > :backgroundrb: > :port: 11006 > :ip: 0.0.0.0 > --- > :schedules: > :server_worker: > :update: > :trigger_args: 1 *

Hi there, We''ve been using previous version of bdrb (drb based one) for a while and it was running relatively OK. We recently attempted to upgrade to the new version to keep up / use supported version but we ended up reverting to the older version. Here are the things that moved us to revert : 1) With the workers we never manage to pass this error: '''' You have a nil

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

Quick question: If I want to schedule different worker methods defined in the same worker to trigger at different times, is this possible? Would the following scheduler yaml work? :schedules: :foo_worker: :worker_method: method1 :trigger_args: 0 */10 * * * * * :job_key: some_key_1 :foo_worker: :worker_method: method2 :trigger_args: 0 */15 * * * * * :job_key:

when working with the scheduler i found that using :trigger_args: 0 * * * * * * in config/backgroundrb_schedules.yml the worker gets only called once. :trigger_args: "0 * * * * * *" works as expected. Maybe this should be changed in the README ? regards tom -------------- next part -------------- An HTML attachment was scrubbed... URL:

I am sure..again I am missing something, but I am trying to start a worker, when backgroundrb starts and it doesn''t seem to work. Here is my config/backgroundrb_schedules.yml file: feed_worker: class: feed_worker job_key: feed_worker_key worker_method: do_work trigger_args: repeat_interval: 20.minutes I even tried this from Rails controller: # def start_feed_worker #

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/

I need to run the same worker''s method twice per day with different arguments. Unfortunately, only the second entry in the schedule is firing. I created an experimental worker to verify this: Worker: class ExperimentWorker < BackgrounDRb::MetaWorker set_worker_name :experiment_worker def create(args = nil) # this method is called, when worker is loaded for the first time

I have two scheduled tasks in my rails app: background_schedules.yml mail_sender_1: :class: :mail_sender_worker :job_key: :job_key_mail_sender_1 :worker_method: :do_work :trigger_args: :start: <%= Time.now + 5.seconds %> :end: <%= 1.years.from_now %> :repeat_interval: <%= 60.minutes %> cleanup_1: :class: :cleanup_worker :job_key: :job_key_cleanup_1

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

I've attached two SIP debugs in reference to bug #116. They are from today's CVS build. 1. pickup.txt is a call from SIP(1) to SIP(2) with SIP(3) picking up the call. After which, SIP(2) rings for about 30 seconds then stops. 2. hangup.txt is a call from SIP(1) to SIP(2) with SIP(1) hanging up before the call is answered. SIP(1&3) are Cisco 7960's and SIP(2) is a Polycom

I''m running the latest backgroundrb mainly for scheduled tasks support. As per the documentation I created the backgroundrb_schedules.yml with the following: simple_label: :class: :document_sorter_worker :worker_method: :do_work :job: :bleh :trigger_args: :start: <%= Time.now + 5.seconds %> :end: <%= Time.now + 10.minutes :repeat_interval: 1.minute Under

Hi there, Backgroundrb is working pretty well for me but I have a job that launches two of the same job, apparently a minute(?) apart from each other. Should this be happening if I have repeat interval enabled with a job_key? It seems like it should wait until the job is finished before launching a new instance. --Backgroundrb_schedules.yml-- city_updater: :class: :city_updater_worker

I''m a big "fan" of BackgroundRB ... 1.0 came along just when my project needed it, and I''ve been very happy. Thanks much for this very helpful piece of software. My question: I have a worker scheduled cron-style as follows: :notification_worker: :notify: :trigger_args: 0 0 8 * * 1,3,5 * I.e., I want to run this particular worker method at 8:00a

Hello! How can I put more data in backgroundrb.yml, if I can? Like that :schedules: :expressz_worker: :sendexp: :trigger_args: */30 * * * * * :data: data1, data2 Thanks a lot! Peter -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080722/64995aa4/attachment.html>

Hey Greg- Yes I am sorry, the new architecture uses fork and named pipes and a bunch of unix stuff to do its magick. Now you may be able to port it to qwork on windows, but I don''t think it is possible :( I''m really sorry about this but I need this thing to be as robust and solid as it can be and in the end windows isn''t compatible. Now you may be able to

Hi I thought this should suspend the task by 1 minute, but it starts immediately: MiddleMan.ask_work( :worker => :bar_worker, :worker_method => :test_method, :trigger_args => { :start => (Time.now + 1.minute)}) Is the start argument not allowed in the new backgroundrb (mine is at rev HEAD (=314))? What can I do about this? I really need to suspend starting the task as I want