search for: backgroundrb_test

Not sure this is known behaviour but it seems that if want to set the environment to, for example, test, and you want to use Active Record you have to both explicitly set the RAILS_ENV and the BackgrounDRb environment. So, if you have a config file backgroundrb_test.yml (as well as the default) and set the environment to test in that, this is what *seems* to happen: $ script/backgroundrb/start # starts backgroundrb in development environment and uses AR in development environment $ script/backgroundrb/start -c backgroundrb_test # starts ba...

...test:plugin". Any idea why I am getting this? Here is the error message: /usr/bin/ruby1.8 -Ilib:test "/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake/rake_test_loader.rb" "vendor/plugins/backgroundrb/test/master_worker_test.rb" "vendor/plugins/backgroundrb/test/backgroundrb_test.rb" "vendor/plugins/backgroundrb/test/meta_worker_test.rb" /home/kenglish/workspace/brbtest/vendor/plugins/backgroundrb/lib/backgroundrb.rb:4: uninitialized constant RAILS_ROOT (NameError) from /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_requ...

Hi All, It might be lack of sleep, but I am struggling to accurately limit our pool size. It seems like I can specify it on the server with the -s command line option and also on the client via the YAML pool_size. Is that right? Which one wins? Our problem is that we are getting about 40 threads on each backgroundrb box and it''s flooring our db and each bgrb box. We want around 8.

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

Hi! My cron-based worker is being indeed invoked by backgroundRB at correct times. But... After several runs it can no longer find DB columns! The same query, which was running OK an hour ago starts to throw MySQL error about unkown column in where clause. If I restart backgroundrb it works for some time but stops working after several invocations. Has anyone epxerienced the similar beahviour?