similar to: memory uses

I have a job that I am starting from a Rails controller in production mode using MiddleMan: MiddleMan.new_worker(:class => :import_ccg_category_worker, :args => { :category_id => @category.id, :remote_category_id => params[:remote_category_id], :description => "Importing CCG products for #{@ category.name}" }) Both of the category ID variables are just basic integers. I

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 all, I just read Ezra''s article on BackgroundRb and decided to use it one of my projects. I installed the plugin into my rails project using script/plugin and then ran rake backgroundrb:setup to copy the yml scripts. Now my backgroundrb.yml looks like ======= --- port: "22222" timer_sleep: 60 load_rails: true environment: development host: localhost database_yml:

What does the method query_all_workers() do? There is no documentation on what this method returns (1.0.1 version). Orion -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080118/9f9b8112/attachment.html

Hi Erza, I am using login engine in my code...and i get the error "uninitialized constant LoginEngine and uninitialized constant LoginEngine", when i try to do a find in the worker code!!! Why am i getting this error? -- nothing much to talk -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello ! 1) I have this error logged by bdrb: undefined method `send_request'' for nil:NilClass framework/packet_master.rb:58:in `ask_worker'' backgroundrb/server/master_worker.rb:59:in `process_work'' backgroundrb/server/master_worker.rb:16:in `receive_data'' backgroundrb/framework/bin_parser.rb:29:in `call'' backgroundrb/framework/bin_parser.rb:29:in

I''m trying to run a single worker that could perform a periodic task for a given user. >From a controller, I imagine something like: def start_job MiddleMan.ask_work(:worker => :foo_worker, :worker_method => :perform_task, :data => { :user_id = current_user.id }) end def check_job @status = MiddleMan.ask_status(:worker => :foo_worker)[current_user.id] end

Hi, A pre-release version of backgroundrb is available now from svn. Download it from here: http://svn.devjavu.com/backgroundrb/branches/version099/ Since this release marks significant migration from existing practices, i intend to keep trunk untouched for a while. There are no install scripts, but you should copy "backgroundrb" file from script directory of plugin to script

I get this error periodically in backgroundrb.log, but only on my production box (the one running ruby 1.8.5) - my dev box doesn''t get this error. As far as I can tell, everything is working ok, despite the error (I don''t really know how to determine if the jobs are getting threaded successfully, but they are running, that I am sure of). Here''s the dump: no

Hi Folks, I have been working to fix BackgrounDRb memory usage as such. Ruby1.8 GC isn''t fork friendly and it seems to use a lot of memory because when you fork, it sets a bit in all the objects in global scope which causes OS to all pages in child process. A classic solution is to use fork and exec, rather than just fork. Its working and pretty stable, but you loose ability to pass

Hi, just updated backgroundrb to release 1.0.1 and am getting this error when trying to start backgroundrb. vendor/plugins/backgroundrb/framework/core.rb:18: uninitialized constant Packet::ClassHelpers (NameError) Just updated from r298 where everything was working fine. If I comment out the offending line then backgroundrb starts but I can''t connect to it from my app. Anyone have any

Hey all, Been reading through all the old posts (and the docs) to familiarize myself but I still feel a bit lost. I''m on trunk and am having a bit of a hard time knowing where to start with the particular I''m trying to solve. So far, I''ve downloaded backgroundrb, done the basic rails setup, created my worker and started it using `script/backgroundrb start`.

Hey All, I am looking for an example of the proper config settings for background rb to run my rails app and my backgroundrb instance on separate machines (or more precisely, to have a rails cluster with one backgroundrb machine). Does anyone have such examples? Thanks! -Noah -------------- next part -------------- An HTML attachment was scrubbed... URL:

Howdy Folks- I''m happy to announce a new release of BackgrounDRb! I have added quite a few new features and included some nice patches from folks on the list. $ script/plugin install svn://rubyforge.org//var/svn/backgroundrb All of the code now stays within the plugin and the start and stop scripts are now just stubs. This makes it easier to tweak or figure out how it works.

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

Hi Folks, I am glad to announce 1.0 release of BackgrounDRb. This would be a major release since 0.2 release of BackgrounDRb. Here is a brief summary of changes: - BackgrounDRb is DRb no longer. It makes use of EventDriven network programming library packet ( http://packet.googlecode.com ). - Since we moved to packet, many nasty thread issues, result hash corruption issues are totally

Hi, I am currently working on a project that requires multiple rails applications (lets call them consumers, since they will consume requests) to exposes long running services that will be executed from a management rails application (the producer of the requests). To do this BackgrounDrb was installed on all the consumers and the producer. BackgrounDrb was configured to on each of the consumers

I am sure..again I am missing something, but I am trying to start a worker, when backgroundrb starts and it doesn''t seem to work. Here is my config/backgroundrb_schedules.yml file: feed_worker: class: feed_worker job_key: feed_worker_key worker_method: do_work trigger_args: repeat_interval: 20.minutes I even tried this from Rails controller: # def start_feed_worker #

Hi All, One can easily code a backgroundrb worker so as it can act as a worker queue, having reached a stable status, perhaps its time we should add this feature. Why? Because if you are already running your application using BackgrounDRb, perhaps you don''t want to manage other solutions when capability to do that is right there with you. Interface? This where i need feedback. You can

In my worker class, when i try to start the worker thread, it throws the error: uninitialized constant LoginEngine - (NameError) /usr/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:123:in `const_missing'' /usr/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:131:in `const_missing''