similar to: MiddleMan singleton issue in start script

i found some questions and answers on mailing lists but there is still a problem - when i want to create new worker from within a worker - ::BackgrounDRb::MiddleMan.new_worker(:class => :second_worker, :args => {:id=>2, :text=>"slave"}) works but when i want to get reference to that object: ::BackgrounDRb::MiddleMan.worker(@second) yields: NoMethodError: undefined

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

I''m trying to test with RSpec (0.7.5), and I have the following code: MiddleMan.should_receive(:new_worker) Every time I run this code, I get this error: undefined method `new_worker'' for class `DRb::DRbObject'' How do I get around this?

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,

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

Hello there, I need a Worker Class to be Singleton-like, that means there must be at maximum one Instance at a time. When a new Request is made to create another worker of this type, it should return and wait for the other instance to be destroyed. what i need to do: i have a worker who needs to do sth with java and openoffice, and it seems when i have more tha one worker simultaneously,

Hello - I am observing that calls to MiddleMan.worker return only after the worker has completed its work. This puzzles me, and I presume that I am doing something wrong. Can anyone make suggestions? Snippets from my code are: class ReportController < SecurityController ... def create_xml_report(report,start_time) constraints = get_constraints(report,start_time,false)

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.

If I add .instance in front of new_worker I get the following error ... but for some reason i cant call new_worker directly...? error: ruby sample_app.rb my sample app :) ./backgroundrb/middleman.rb:440:in `ex'': undefined method `synchronize'' for nil:NilClass (NoMethodError) from ./backgroundrb/middleman.rb:401:in `[]'' from

Ok let this be a lesson to the general public. If you want to look as idiotic as I do right now do the following: Stay up all night and attempt to debug code the next day without coffee Patch the wrong file RAILS_ROOT/scripts/backgroundrb/start instead of one in plugin dir. Create a patch in the right location containing nothing but an extra space Send it to the whole Ruby community AND file a

An action handler (select_person_by_name) in my controller class assigns into session, and then does a redirect_to. I get the error "TypeError (singleton can''t be dumped):" followed by a stack trace that doesn''t cross my code. Google tells me this is ordinarily caused by assigning a singleton instance into session, but what I''m assigning is an ordinary String.

I just updated backgroundrb to the latest version, and now I get this: uninitialized constant MiddleMan /usr/local/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/ active_support/dependencies.rb:123:in `const_missing'' /usr/local/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/ active_support/dependencies.rb:131:in `const_missing''

Hello, after having changed the session store from CGI::Session::DRbStore to CGI::Session::ActiveRecordStore, I keep getting an error which says: singleton can''t be dumped However, my session object is not a singleton. Does anybody know what causes this error? I can also post the full stack trace, if required. Greetings Michael Kastner

Hi, I am doing an integration with commission junction using SOAP to get the result. It is working fine for me. My problem is I have to add the pagination so I have used will_paginate for pagination. For each page I am doing a call to commission junction and getting the result which make a performance bottleneck for my application. To solve this I have decided to store the response in session and

Author: meem Repository: /hg/zfs-crypto/gate Revision: 40aa11f97fc0148333e53145eebb12da7e84dec5 Log message: PSARC/2006/289 Rationalized IFF_NOFAILOVER for IPMP Singleton 6397456 IPMP needs to support *just* link-based failure detection with singleton Files: update: usr/src/cmd/cmd-inet/usr.lib/in.mpathd/mpd_main.c update: usr/src/cmd/cmd-inet/usr.lib/in.mpathd/mpd_tables.c update:

Hi list, I''m having some issues getting backgroundrb to play nice with more than one mongrel. When I run my app on a single mongrel instance it works fine. I have two different problems show up in my backgrounrb_server.log. The top of the backtrace is shown here: 20070130-12:03:03 (92473) failed to find slave socket - (RuntimeError) 20070130-12:03:03 (92473)

Hi all, I know it may not have much sense thinking about a Singleton Pattern in an R application which doesn't use any OOP facilities, however I'm curious to know if anybody faced the same issue. I've been googling but using "singleton pattern" as a key word leads to typical OOP languages like Java or C++ among others. So my problem is that I'd like to ensure some very

Hi everyone, I''ve a class that try to spawn two workers, every 5 seconds. The code is something like: while true do MiddleMan.new_worker(:class => :researches_worker,:job_key => :researches) MiddleMan.new_worker(:class => :products_worker,:job_key => :products) sleep(5) end I''m using ":job_key", so if a worker hasn''t already ended its work

I have a test case where I''m stubbing one method (''jobs''), and mocking another (''new_worker'') MiddleMan.stubs(:jobs) MiddleMan.expects(:new_worker).with{|args| args[:class] ==:download_worker} MiddleMan.jobs() The above code results in an error ("The error occurred while evaluating nil.[]") - calling ''jobs'' results in

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