similar to: Simple way to detect from rails if backgroundrb server is running

Hi, it probably is a noob question but I''m confused by this error message: active_support/dependencies.rb:478:in `const_missing'': uninitialized constant Invoice::ApplicationController Situation: I have an InvoicesController with a create method that in turn calls upon a MiddleMan.worker(:billing_worker), which in turn finds an Invoice and calls upon @invoice.print_invoice

Hi, I have my rails sites tricked out with capistrano, and backgroundrb, so I can easily use the ant tasks, but I would like to be able to start and stop backgroundrb from within rails. I have a few reasons for this: 1. Using fastcgi, backgroundrb would start under the apache user and the same mod_security context as apache, instead of my developer account which has many more privileges. 2.

Trying to use backgroundrb to process and insert a large list of bulk records, but when I try to use it with the batched_sql_fu plugin installed in vendor/plugins, I get the following error: ---SNIP--- /Users/jdonalds/Sites/3dial_ads/config/../vendor/plugins/ batched_sql_fu/lib/batched_sql_fu/active_record.rb:22:in `alias_insert_sql_to_batched_version!'': undefined method

Hi I just tried to move my project to rails 1.2.1 on my locomotive development setup. It seems that backgroundrb is not willing to start up anymore. If I switch locomotive back to 1.1.6, everthing is fine. This is the error I get while attempting to start backgroundrb: /Applications/Locomotive2/Bundles/standardRailsJan2007.locobundle/

I found this stack trace in my logs. My worker name is MiscWorker, and Qualifier is a Rails model. uninitialized constant MiscWorker::Qualifier: /Users/bryan/ Workspace/sandbox/scraper-trunk/config/../vendor/rails/activerecord/ lib/../../activesupport/lib/active_support/dependencies.rb:476:in `const_missing'' /Users/bryan/Workspace/sandbox/scraper-trunk/lib/workers/

Hello all, We''re currently running version .1.x in our environment. We would like to move to .2.x to take advantage of some of the improvements made running in a multi-process environment. We deploy to a linux environment but develop locally in Windows. I''m aware that a number of people have reported the ability to run .2.x of backgroundrb inside cygwin, and for the most part,

Hi all, Just had an interesting production failure while updating my Rails application - a bunch of code previously in config/environment.rb was put into config/initializers. That resulted in me having to wrap some code in config/environments/production.rb into an after_initialize do ... end block When backgroundrb was run against that code, the setup done in that after_initialize block

When I call ask_status on a worker that has not been started I get and exception of type BackgrounDRb::BdrbConnError, which is fine. I can deal with that, but I also find that the backgroundrb process dies as well. The scenario is simple: Call ask_status on a worker that is not auto loaded. I used a job_key, in case that makes a difference. -------------- next part -------------- An

BackgrounDRbers: We pass a data batch to a background task for processing. When it finishes, our GUI updates correctly (using the results hash). But the data records don''t appear in the Rails connection to the database. Our stack is the HEAD BackgrounDRb, Rails 1.1.6, MySQL, and Apache/mongrel. As soon as I whack the background process with script/backgroundrb stop, the data records

So, if I wanted to have backgroundrb running on two servers, that would just be a matter of creating two different backgroundrb.yml configuration files (one for each server) and starting backgroundrb on both servers, right?

Hi all My problem is that: With reference to http://backgroundrb.rubyforge.org/ 1---I have download backgroundrb from http://opensvn.csie.org/ezra/rails/backgroundrb to my vendor/plugin in my application folder. 2-- after that I used the command to run :-rake backgroundrb:setup -- trace From my application

Hello all, I''m using BackgroundRb 0.2.0 (standalone) and in the do_work method of my worker, I''m working with objects from my Rails application. So in my config/backgroundrb.yml file, I added this line: :load_rails: true I think my worker isn''t doing what I want him to do. So I opened the console and read these error lines: # ruby script/backgroundrb console

Hi everyone, I noticed that script/backgroudrb requires config/environment which causes the backgroundrb server as well as the log worker to ''bloat'' to 35MB each. I am kind of sensitive to memory issues, so I patched the code and essentially moved the require of environment from script/backgroundrb to the meta_worker. Everything seems good and now both backgroundrb server and

After upgrading to backgroundrb 0.2.x, Rails barfs lstat errors left and right when using the console or webrick or mongrel on win32. We run our site on a Linux server, so I''m not trying to get backgroundrb to work on a win32 machine. I just want to quietly stop loading itself if it detects that it''s on a win32 machine so that the rest of Rails can continue to load. Most of

Hi, I''ve been playing with backgroundrb to batch process a bunch of images on a rails server. The process is working fine when backgroundrb is started from the command line, but seems to choke occasionally (well, quite often) when running as a service. It seems to get stuck on the following line when moving files: FileUtils.move(src, dest, :verbose => true) with the error: Bad

This might be a really simple question, with a simple solution. I have two rails apps running on the same box. Right now I am starting two Backgroundrb servers (11006 and 11007). Wondering if it might be possible to run only one and have the second app point to the first app''s server? TIA, Kit

Hi, If I start backgroundrb with rails_env = production, and then run my test suite, is it true that my background tasks will run against the production database? Can I prevent this from happening when I mistakenly end up with a combination like this? Thanks Joerg -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because

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

Greetings! Has anybody tried running the ''old'' version of BackgrouDRb (the repository on rubyforge.org) on Rails 1.2.1? Any reason to think it won''t work? Thanks! Bill -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20070130/93d4cd89/attachment.html

I added the following in my rails environment: ENV[''TZ''] = ''UTC'' Background rb does not have the same time as my rails app. In fact it is a few hours behind. Any idea why this is? Thank You, Ben Johnson E: bjohnson at contuitive.com -------------- next part -------------- An HTML attachment was scrubbed... URL: