similar to: Problem with drbundumped?

Hi, I am getting my hands on trying the cool BackgrounDrb plugin. Following various discussions and suggestsion, I included "include DRbUndumped" in my ActiveRecord model. However, the following exception occurs after I tried this and hit the page that uses this model. Does anyone know why this is so? Is it possible that an object cannot be DRbUndumped (that would mean, we

I have a simple question. Let''s say I do this in one of my models: after_save drb_conn.some_method(self) end When that object gets over to the background process is it the exact same as?.... Model.find some_id #in the background process As far as my background process is concerned passing the object is not any different than passing the id and using the find method? Because

I have a pretty strange problem. Here is basically what I have to demonstrate my problem: class Event < ActiveRecord::Base def after_create AnotherClass.find_event(id) end end class AnotherClass < ActiveRecord::Base def self.find_event(event_id) e = Event.find event_id end end Here is the catch 22 and it''s quite annoying. Basically ActiveRecord puts to whole save

In a previous email you wrote this: Glad you''re getting some use out of the plugin ;) ActiveRecord does have some issues with threading and concurrency that can sometimes cause that error you are seeing. Open up your script/backgroundrb/ start file and comment out the following line: ActiveRecord::Base.allow_concurrency = true Make sure you do that up in your main app script folder

Since MiddleMan is an uninitialized constant in a worker how do you create new workers inside a worker? Thank You, Ben Johnson E: bjohnson at contuitive.com O: 800-341-6826 M: 817-229-4258 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20060731/75a77fa6/attachment-0001.html

Hi, I have "include DRbUndumped" in one of my model classes. Whenever my app accesses the session I get the following: can''t dump /usr/lib/ruby/1.8/drb/drb.rb:395:in `_dump'' /usr/lib/ruby/1.8/pstore.rb:349:in `dump'' /usr/lib/ruby/1.8/pstore.rb:327:in `transaction'' /usr/lib/ruby/1.8/cgi/session/pstore.rb:90:in `update''

Hi Ezra, Thanks for the great work on BackgrounDRb. I have come across a couple of problems. 1. I wanted to define a simple class in the worker file to wrap up and pass back some data to my controller. It seems that if I create the class either inside or outside of my worker class (in the same file) it gets wrapper by a DRb::DRbUknown object and therefore cannot be accessed from my controller.

I''m getting strange data back from my worker whenever I run our rails app with more than one dispatcher under lighttpd. just to give some info on what the app does: user submits data to rails app. rails app hands off data to worker, which goes and does it''s thing, storing results in an array of response objects (the array is an attribute of the worker). the response object

got a wierd problem maybe someone can help with. whenever i try to pass an array or AR objects to my worker, i end up with a DRb object in the worker...here''s an example class SearchWorker < BackgrounDRb::Rails attr_reader :resources def do_work(resources) logger.info resources.inspect end end class SearchController < ApplicationController def start_search

My application has one central database + Rails server and many distributed GUI clients. The remote clients need to read and update different collections of ActiveRecords. They also need to submit fairly demanding calculation + database update requests. Have you designed a similar Ruby application? What did you do? I''ll try to summarize the approachs I''m considering

Hi. I thought that BackgrounDrb was the perfect solution for my long running report production tasks. But I can''t seem to get anything useful back out of it. I set up a simple test worker that just does class TestWorker < BackgrounDRb::Rails attr_reader :pupil def do_work(args) @progress=0 @pupil=Pupil.find(3) sleep rand*10 @progress=100 end when I try to

Hi *, are there some special settings except of "load_rails: true" to make ActiveRecord models accessible within my workers? I''ve just installed the latest version of this great plugin, but I keep getting undefined method [] for #<DRb::DRbUnknown:0x12345> (line 105 in backgroundrb.rb) when one of the arguments for the worker is an ActiveRecord object. I assume that

I tried installing BackgrounDRb today. Followed the readme, made a little worker for myself and executed it within the code. But I keep getting this error. I must''ve gone over the README a zillion times. Any idea what it is? undefined method `[]'' for #<DRb::DRbUnknown:0x2501bd4>

I have a very strange problem here. I do not get this. So any help is greatly appreciated. Basically I have a model that calls a method in the background process in the "after_save" method. Let''s call the model products. So what happens is this: 1. I create a new product. 2. Everything works and the product is saved with id 13. 3. A method is called in my background

Friends- I see more and more folks wanting an application wide context object that will work regardless of server software(webrick,mongrel, fcgi''s, scgi''s) This can be a very useful technique if done correctly. Here is a little info that I have gleaned on a great way to do this type of thing. -----Easy AppServer---------------- An easy way to get yourself an

Hi, Does it make sense to test a worker class by calling Middleman.new_worker? Or should I just be testing the functionality in the do_work method, with, say, a mock object. This seems like a really ugly DRY violation: you''d need to keep the code in the mock and the real worker in sync. That''s the philosophical half of my question. In fact, until someone tells me why I

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

Hi All, I''m using Backgroundrb as a general purpose long-running-task back-end (upload processing, email sending, etc), and it''s been a great solution. However I''ve recently run into some some intermittent connection issues that have me baffled. I''m running on apache2/fcgid and the problem occurs in both devlopment and production mode. The problem seems to

Friends- I''m happy to annouce the first alpa release of BackgrounDRb. This is a small framework for managing long running background tasks that allows for ajax progress bars and more. It also serves as an Application wide cache and context store for when you need something like sessions but shared between users and multiple backend processes like fcgi''s or mongrels.

hi, i am using drb and it is working fine on my local pc on windows.. and after uploading the code to the server it was working for sometime but now it gives me error every time i invoke 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''