Displaying 20 results from an estimated 3000 matches similar to: "Connections"
2007 Dec 18
5
querying status of worker with job_key
Hi,
Is it possible to start a worker with job_key and then ask_status of that
specific worker with the job_key?
MiddleMan.ask_work(:worker => :auth_worker, :job_key=>''1'',
:worker_method => :auth)
and then
MiddleMan.ask_status(:worker => :auth_worker, :job_key=>''1'')
>From my testing of the new backgroundrb, asking status using job key
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
2008 Jan 11
18
getting started
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`.
2008 Jan 10
8
Worker suicide
I have a worker which wants to delete itself after it finishes its
work- how can it do that?
Best Regards,
Danny Burkes
2007 Dec 22
1
Backgroundrb Question
If I have a worker and everything set up and I call:
MiddleMan.ask_status(:worker => :foo_worker)
MiddleMan.ask_status(:worker => :foo_worker)
MiddleMan.ask_status(:worker => :foo_worker)
three times in quick succession. Will the tasks be queued up and
executed as the previous one finishes? Or is this going to ignore the 2
bottom requests? How does this work?
Do I absolutely need to
2008 Mar 19
2
problem with worker status
Hi,
I have a page were users can start jobs that may take several hours to
run. BackgrounDrb is perfect for me and seems to be working well most of
the time but some times I have the following problem:
My worker is set up like this:
class UploadWorker < BackgrounDRb::MetaWorker
set_worker_name :upload_worker
set_no_auto_load(true)
def create(args = nil )
file = args[:file]
2007 Dec 21
7
Using my models
I''m working on upgrading my app to the latest version of backgroundrb.
Everything went find until I tried to execute my tasks.
Here is my simple worker for testing:
class MscWorker < BackgrounDRb::MetaWorker
set_worker_name :msc_worker
def create(args = nil)
# this method is called, when worker is loaded for the first time
end
# Send a message to everyone
def
2007 Apr 30
1
monit config?
Anyone have a a good monit config section for bgrb?
I''m thinking something like this:
check process backgroundrb with pidfile
/var/www/apps/foo/current/log/backgroundrb.pid
start program = "/var/www/apps/foo/current/script/backgroundrb start"
stop program = "/var/www/apps/foo/current/script/backgroundrb stop"
if failed host 127.0.0.1 port 2000 then restart
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 Nov 14
7
BackgrounDRb version 1.0RC1 available now
Hi Folks,
BackgrounDRb is a Ruby job server and scheduler. Its main intent is to be
used with Ruby on Rails applications for offloading long-running tasks.
Since a Rails application blocks while serving a request it is best to
move long-running tasks off into a background process that is divorced
from http request/response cycle.
This new release of BackgrounDRb is also modular and can be used
2008 Jan 17
3
periodic scheduling
I''ve been using backgroundrb since back in March 2007 or so. It''s
been working mostly OK for me, but since the old version doesn''t seem
to work out of the box with rails 2.0 for me, I decided to test out
the latest version.
So, I''m looking at the scheduling, and trying to figure out the best
option for what I want to do. What I have is a set of workers that
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 18
1
Backgroundrb crash calling ask_status when worker not running
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
2009 Jan 06
1
ask_status/register_status deprecated???
Hi,
I''ve been using bdrb for a while and just recently found the need to use the
ask_status/register_status functionality of my worker.
This is the error I get whenever the register_status method is encountered:
...lib/workers/session_worker.rb:10:in `create'': undefined method
`register_status'' for #<SessionWorker:0xb6e7d52c> (NoMethodError)
from
2008 Mar 21
5
State of backgroundrb (dupe?)
Hi, pardon if this is a duplicate mail, I forgot to click the
subscription link the first time around.
I''ve been using backgroundrb for a while now (older version) and I''ve
had so many headaches because of it that I began looking for a
replacement technology. And then I saw the new and shiny backgroundrb
website, looking good!
Initially I used the version maintained by
2007 Dec 13
1
Possible Bug & Question
Hi there,
Amazing changes! I really like what you''ve done with BackgrounDRb and I hope
you continue developing it, since it was definitely somewhat languishing
before.
One small error stuck out for me, though. The create method requires an
argument even if one isn''t used, such that if you have:
def create
@results = Hash.new
end
The server throws an error about trying to
2008 Apr 14
6
Good news: BackgrounDRb now works on Windows
Hello all,
I have some good news to announce. I have made some changes to a local copy
of BackgrounDRb 1.0.3 (actually most of the changes were in Packet 0.1.5)
and I''ve got it working on Windows. From what I''ve read, this is the first
time it''s worked on Windows in a year and a half, since 0.2 was released.
In my research I can see that a number of people have asked
2008 Jun 10
3
Backgroundrb fixes for transfering large amounts of data
Hemant
We''ve continued testing our application with backgroundrb and found a
couple of other problems when transfering large amounts of data. Both
of these problems are still present in the github version of code.
The first problem is an exception in the Marshal.load call in the
receive_data method in the Packet::MetaPimp class. The root cause is in
the BinParser module, in the arm of
2006 Apr 09
2
Substruct v0.6
I just put the finishing touches on Substruct v0.06. As always, you can
check out a demo over at http://substruct.subimage.com/
What''s new?
Version 0.6
---------------------------------------
Added:
- Tagging for products
- Maintenance of product tags
- Automatic image thumbnail / small size creation via RMagick
Updated:
- Better shopping cart experience with AJAX cart
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