Displaying 20 results from an estimated 20000 matches similar to: "Exceptions in workers"
2007 Dec 21
3
Jobs running too slow
Say I have a job that runs every minute, but it takes longer than a
minute to execute. Will it start a new job every minute?
If it does, then how would I make a job that sleeps for a certain
amount of time, then restarts? I have a job that could take an hour
or two to complete, and I don''t want to have multiple copies of that
job running at the same time.
Joe
2007 Apr 18
5
[BUG] worker stopping abruptly
I have been facing this damn ugly issue since quite sometime.
So this worker reads RSS feed from Yahoo news and stores it in a DB.
The worker is scheduled to run at every 40 minutes and my
background_schedules.yml looks like this:
feed_worker:
:class: :feed_worker
:job_key: :feed_worker_key
:worker_method: :do_work
:trigger_args:
:start: <%= Time.now + 5 %>
2007 Dec 17
7
Get "some read error" on calls to worker
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
2007 Dec 06
10
Feedback on RC2
I tried to upgrade my existing application to RC2 last night. Like many, I
use this mostly for running scheduled tasks. For the moment, I''ve abandoned
the effort, but am looking forward to being able to use this. Feedback
below:
First, the reason I was looking forward to this upgrade was to use the
threaded scheduler. I have an application with long-running tasks. I found
that
2008 Jan 18
8
Query All Worker
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
2007 Dec 19
6
thread_pooling sleeping
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
2006 Jul 06
5
memory uses
Hi All,
I have this small doubt. Does backgroundrb have anything to do with
dispatch.fcgi?
some dispatch.fcgi are taking memory as much as 186 MB ....
this is monstrous man...
Also, if i put load rails environment with backgroundrb.yml file to be
false.What will happen? i just loses access to db through ActiveRecord
right?
I can still use normal mysql gem to access db and modify the
2007 Nov 07
2
workers cleanup
Hi,
I''m using backgroundrb 0.2.1 and having problem with worker processes
staying around when the rails application does not explicitly delete
them.
Is there a way to automatically delete the worker processes when it
has completed the job?
Also does killing the process manually (using kill command) harm the
backgroundrb server? I have some occasions where the backgroundrb
server just
2007 Dec 15
10
1) Error 2) sending request to a specific worker
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
2008 Jun 04
2
Handling exceptions
Is there a convention for handling exceptions within BackgrounDRb workers?
For example, I have a worker which does some asynchronous data processing
(*not* a scheduled worker) based on some things in the database. However,
if an exception is raised within that worker, then the process for that
worker is killed off. Ideally I would want that worker to just silently
fail and be optimistic that it
2008 Jan 09
6
[PATCH] x 2 - Fix for "null pointer exception" when ask_status is called before worker is run, and docfixes
Sorry for attaching patches in emails to the mailing list, but I''m still
unable to login to Devjavu for Backgroundrb (I''m able to login just fine for
Merb''s Devjavu and submitted a ticket successfully).
Anyway, I encountered a bug when trying to #ask_status of a worker before
it''s run (or rather, before its result_hash has been set to something). Not
sure why
2008 May 04
12
best approach to managing workers and getting status
Hi,
I am using backgroundrb to process audio files from a rails
controller. Currently a new worker gets created every time the method
is called on the worker, using this code:
@job_key = MiddleMan.new_worker(:worker
=> :audio_file_worker, :job_key => Time.now.to_i)
MiddleMan.worker(:audio_file_worker,
@job_key).make_new_audio_file(params[:release_id])
I need to create the new
2007 Dec 14
4
Error when loading backgroundrb
I''m getting the following error (when doing script/backgroundrb start)
on my local machine, which is running os x 10.4.11. However, it
works just fine on my linux server.
RAILS_ROOT/vendor/plugins/backgroundrb/lib/../framework/nbio.rb:64:in
`dump_object'': undefined method `write_nonblock'' for #<UNIXSocket:
0x135b5f4> (NoMethodError)
I just grabbed the
2006 Nov 07
2
start a worker when bdrb starts
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
#
2008 May 30
5
Upper limit to number of jobs queued by BDRb?
I use BDRb to process RSS feeds for users on my site (http://feedflix.com).
I have a batch job that queries the DB for records that haven''t been updated
in the last so many hours and kicks off a background job for each of them.
If N records are returned by the DB, N background jobs gets queued and get
done serially. As long as N is 255 or under, everything works like a charm.
2007 Nov 02
10
pre-release version of backgroundrb available now from svn
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
2007 Dec 10
21
BackgrounDRb 1.0 pre-release available now
Hi Folks,
We are glad to announce shiny new release of BackgrounDRb, which will
soon become 1.0.
A quick summary of changes:
- BackgrounDRb is no londer DRb, its based on event driven network
programming library packet ( http://www.packet.googlecode.com ) .
- Since we moved to packet, many nasty thread issues, result hash
corruption issues are totally gone. Lots of work has went in
making
2007 Dec 22
2
Implementation details for worker Queue
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
2008 Apr 09
3
reload_on_schedule
Hello,
Does reload_on_schedule force the worker to be reloaded even if it is
already running?
Or does it just load the worker if its not running when the schedule fires?
I want to load the worker at the scheduled time if its not running, but I
don''t want to reload the worker if its already running.
Make sense?
Thanks,
Scott
2007 Dec 08
3
Multiple Worker Methods on Different Schedules
Quick question: If I want to schedule different worker methods defined in
the same worker to trigger at different times, is this possible? Would the
following scheduler yaml work?
:schedules:
:foo_worker:
:worker_method: method1
:trigger_args: 0 */10 * * * * *
:job_key: some_key_1
:foo_worker:
:worker_method: method2
:trigger_args: 0 */15 * * * * *
:job_key: