similar to: Query All Worker

Can anyone explain why BackgrounDRb is switching form DRb to SMTP protocol? That seems like a lot of overhead to add to the messaging back and forth? Orion

Hi, Would greatly appreciate some help with this. Is the following error caused by an incorrect worker name? You have a nil object when you didn''t expect it! The error occurred while evaluating nil.send_request /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_master.rb:44:in `ask_worker'' Here''s what I''m doing in my rails console.

Hi, Thanks for the help getting the new backgroundrb working, things are working fabulously now. I have two questions: 1) I have a few basic methods I need available on all my workers in order to communicate properly with my application... it seems to make the most sense right now to subclass BackgrounDRb::MetaWorker, or make a mixin module, because I''m actually extending some

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

Hi all, I''ve been having trouble for a long time with backgroundrb processes that suddenly vanish without a trace. What happens is that at some point I discover that all the backgroundrb processes are suddenly gone. Nothing special is seen in any of the log files. This has happened intermittently for a long time, and I was hoping that upgrading to 1.0.4 would somehow help me out, but

I have a worker which wants to delete itself after it finishes its work- how can it do that? Best Regards, Danny Burkes

Is it expected that MiddleMan.ask_stats will return a status for a worker that has been MiddleMan.delete_worker''ed? The worker isn''t showing up in MiddleMan.query_all_workers, so it seems that is shouldn''t have a status either. Is there a way to define a callback that is called at deletion, to reset the status, or do I need to write my own method to reset the status

Hi, I am pushing some updates and fixes that addresses much of the issues that we talked about since last couple of days. 1. Use configuration option :debug_log: false to disable backgroundrb_debug.log. 2. As shown below, use lazy_load option to disable aggressive loading of models ( and somewhat stupid too). 3. MiddleMan.delete_worker(:worker => :foo_worker) will now ABORT the worker, it

What might be causing this error? I see it once in 2-3 days and it goes away when I restart backgroundrb. Quoted below is my backgroundrb_server_11007.log file. Can I do anything to avoid this? Thanks, Raghu ================================================================================== /usr/lib/ruby/1.8/monitor.rb:224:in `mon_exit'': stack level too deep (SystemStackError) from

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

Dear R-help, I'm very sorry to ask 2 questions in a week. I am using the package 'crr' and it does exactly what I need it to when I use the dataset a. However, when I use dataset b I get the following error message: Error in drop(.Call("La_dgesv", a, as.matrix(b), tol, PACKAGE = "base")) : system is computationally singular: reciprocal condition number =

I''m running the latest from svn (rev 285). I''ve been having a problem launching a process repeatedly. What happens is that I get a debug message "some read error" and then the worker refuses to run again. I''ve stripped my worker down to just doing a puts and it still happens. Like the other threads I want to launch my workers as needed, however I get the

Hi, I run the "Unit testing", Then The "Actionview::Testcase" is failed. i.e i am getting the error as below, 1) Error: test_tablename(ActionView::TestCase): TypeError: wrong argument type Class (expected Module) /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/action_controller/helpers.rb:76:in `include''

Hi, I have successfully crossed all the hurdles to install Ruby on rails on a redhat 5 Linux based system. But the last and the biggest hurdle i am facing at this moment is installing backgrounrb :( I followed all the steps from the http://backgroundrb.rubyforge.org/ 1. sudo gem install chronic packet 2. script/plugin install svn://rubyforge.org/var/svn/backgroundrb [IMP:::: I had to drop

Hi! I''m using the latest&greatest backgroundrb with rails 2.0.2 on ubuntu dapper. I''ve made an app that lets you run a query on several servers at once, which are selected at runtime. Therefore, for each server that is selected, I spawn a new worker and assign its work. After everything is completed, the workers are deleted. I often get this error:

Hi all, I''m trying to replace an OpenWFEru/daemons-based infrastructure, with the goal being to be able to communicate with the workers to a) monitor current state and to b) initiate new actions. The short version on why these are daemons and not transient workers (that start up and shut down when they''re done with a particular task) is because they''re subscribing to

I''m using a plugin which adds a method to ActiveRecord::Base http://similetimelinerailshelper.googlecode.com/svn/trunk/simile_timeline/ This adds an "acts_as" type declaration to the Models, via the file in vendor/plugins/simile_timeline/lib/simile_timeline.rb Rails is working with these declarations, and they are being used successfully in ''regular

Seeing a build problem after updating my git tree: $ git remote -v origin git://git.samba.org/samba.git (fetch) origin git://git.samba.org/samba.git (push) $ git pull $ ./configure ... $ make clean WAF_MAKE=1 python ./buildtools/bin/waf build ./buildtools/wafsamba/samba_utils.py:397: DeprecationWarning: the md5 module is deprecated; use hashlib instead

Hi All, I''ve been developing a rails app using the Bitnami RailsStack ( http://bitnami.org/stack/rubystack) and it has always worked as advertised. That is until I have tried to get BackgrounDRB up and running. I have followed the steps given on the plugin''s project page, each seems to work. I the plugin install works, I can generate workers etc, but when I start the backgrounDRB

We''re encountering a failure with Mocha 0.5.6. We had this expectation: game_version.expects(:attributes=).with(:game_file => kind_of(GameFile), :game_id => @game.id) This expectation was passing with 0.5.5, but fails with 0.5.6. I added this test to parameter_matcher_acceptance_test.rb, which passes in 0.5.5 and fails in 0.5.6 def test_should_match_nested_parameters