search for: my_work

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 g...

...sn''t queued up, and c/d never start. I''ve also had ''b'' start but never finish. (May have been due to do_work deleting the worker as ''a'' finished in that case.. figured delete was neccessary to have the other jobs start, but no..) lib/workers/my_worker: class MyWorker < BackgrounDRb::Worker::RailsBase def do_work(args) logger.info("MyWorker#do_work. args: #{args}") sleep(60) logger.info("MyWorker#work done, deleting self. args: #{args}") # probably shouldn''t call self.delete here, as we reuse t...

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

I''ve been checking out all the async gems and plugins for Rails, and decided to give BackgroundRb a shot. Unfortunately, I''ve not even been able to get past the initial stages. Whenever I call MiddleMan.new_worker, it invariably returns nil. The log file remains empty. I''ve only tried this from the console so far. If I can''t even do this successfully,

I recently switched over to v1.0, and things are rolling along pretty well. However, one thing that has always been a little confusing to me is knowing when to use thread_pool. Since most of my bgrb workers are called from my web app to process rather than being scheduled, I''m using the thread_pool for every call. Unfortunately, that means that I have to split up workers by how many

Greetings all, Unit tests are passing, but I''m having mucho problems getting brb to run without exceptions for more than 6 hours. I''m seeing a mixture of the following 2 exceptions: 20070605-11:26:56 (21497) failed to find slave socket - (RuntimeError) 20070605-11:26:56 (21497) /usr/local/lib/ruby/gems/1.8/gems/ slave-1.2.1/lib/slave.rb:435:in `initialize''

...tart it manually and that doesn''t work either. To get it going again I have to restart the server. I don''t know how else to explain what is happening, but will be happy to answer any questions if it will help. Just for starters here is my YML file that configures the schedules My_worker: :class: :my_worker_class :job_key: :my_job_key :trigger_args: 0 50 1 * * * * Thanks. Peer Allan Sr. Web Developer, e-Business CanadaDrugs.com Group of Companies 16 Terracon Place Winnipeg, MB, Canada R2J 4G7 Phone: (204) 654-7951 Cell: (204) 781-8719 Fax: (204) 654-7910 www.canada...

...39; You have a nil object when you didn''t expect it! The error occurred while evaluating nil.send_request /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_master.rb:44:in `ask_worker'' '''' 2) It is not clear the difference between Middleman.worker(:my_worker, key).ask_status and using the nonexistent method Middleman.worker(:my_worker, key).mumbo_jumbo - they both return nil. I understand that is related to one way invocation (asynch) but this just too loose and easy to mixup things. 3) Unit testing - we used backgroundrb_mock.rb that mocks new_work...

Hello, I am trying to make DRb calls to a external server from a backgrounDRb worker, but I''m getting always the next exception when I make the remote call. > ERROR: > drbunix:///tmp/backgroundrb.11175/experimenter_worker_3e899de945f0803a82cd257cfac316d0_0_0.0738904928422051 > - #<Errno::ENOENT: No such file or directory - >