search for: email_work

...the process.. error--- uninitialized constant EmailWorker::Notifier - (NameError) /usr/lib64/ruby/gems/1.8/gems/activesupport-1.4.2/lib/active_support/ dependencies.rb:477:in `const_missing'' /data/flywheel/releases/20071214170355/config/../script/ backgroundrb/../../config/../lib/workers/email_worker.rb:14:in `do_work'' /data/flywheel/releases/20071214170355/config/../script/ backgroundrb/../../config/../lib/workers/email_worker.rb:13:in `each'' /data/flywheel/releases/20071214170355/config/../script/ backgroundrb/../../config/../lib/workers/email_worker.rb:13:in `do_work'...

...ilently fail and be optimistic that it was an edge case that won''t happen every time the worker is invoked. As of now, I''ve just added some basic exception handling to log the error for future inspection like so: class EmailWorker < BackgrounDRb::MetaWorker set_worker_name :email_worker def run(data = nil) do_stuff rescue Exception => ex logger.info ex end end Is this generally the practice for doing exception handling within workers or is there another approach? Regards, Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL: &...

Hello, I''m trying to send emails from a backgroundrb worker and the email doesn''t send. I get no log messages in the sendmail log or the system log, nothing in the backgroundrb logs at all, nothing in the production log. Below is my code for each component worker: class QuizReviewerWorker < BackgrounDRb::MetaWorker set_worker_name :quiz_review_sender def create(args =

In response to my Rails Weenie post today[1], someone mentioned that I try BackgrounDRb to help take the strain off my application. 1: http://rails.techno-weenie.net/question/2006/7/13/nested-loops- best-way-to-send-messages-to-blog-subscribers I''ve just tried to install and use BackgrounDRb with my app, but I''m afraid that I''m not too versed in running processes