Displaying 10 results from an estimated 10 matches for "jobkeys".
Did you mean:
jobkey
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]
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 Jan 27
0
Debugging stale backgroundrb
Hi!
As you might remember I''m having a problem of backgroundrb stopping
calling my workers after some period of time. I tried adding logging
to backgroundrb source code but it didn''t help. So, after digging
through internet I''ve found several gdb tools and here''s what I''ve
discovered:
After attaching to a backgroundrb ruby process it turns out that it
2006 Sep 22
1
how about the global data when multiple backgroundrbs ?
Ezra,
Suppose a chatroom application, a RailsApp + 2 backgroundrbs: MiddleMan1&
MiddleMan2, running in 2 machines.
When Chater1 login, RailsApp call MiddleMan1 to get something about
Chater1 from db to memory, like his contacts or other personal settings.
When Chater2 login, RailsApp call MiddleMan2 do the same thing.
But who is reponsible for the Global Data? like a Online Chaters
2007 Jul 29
4
Server dying with perpetual "Connection reset by peer"
I''m at a loss to explain a very strange error I''m getting.
This seems to happen on our production system where we have a
backgroundrb server sharing a host with a Rails app running on
Mongrel. The first one or two, occasionally three, calls to a worker
(direct MiddleMan calls from Rails, not scheduled) succeed, but
afterwards, the server fails to initialize new workers.
2006 Jul 01
9
BackgrounDRb New release.
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.
2006 Sep 21
1
backgroundrb scalability
i''m in a team that is currently developing a web 2.0 application that really
needs to scale in the very near future.
we are using backgroundrb for some of the server tasks.
currently, we have two servers (in RubyOnRails) that connects to a single
backgroundrb daemon.
is there a way that we can run multiple backgroundrb and have the servers do
a round robin on them to retrieve a worker
2007 Jan 19
6
Stopping DRb after using BackgrounDRb::MiddleManDRbObject.init
Hi,
I''m having a problem where connections started through
BackgrounDRb::MiddleManDRbObject.init are not stopped, resulting in an
ever growing established connections between my Mongrels and remote
backgroundrbs
I added DRb.stop_service to my code executed after requests that init
MiddleManDRbObjects but that does not help.
Any ideas?
Thanks,
Robert Bjarnason
2007 May 22
4
Recommendations for eternally-running backgroundrb workers?
I''ve got some workers that I want to have running all the time. Right
now I''m just launching them manually, by requesting a special page in
my rails app that includes lines like:
MiddleMan.new_worker(:class=> :receiver, :job_key=>:r,
:args=>{:sleep_time=>10})
This strikes me as a really weak way to fire up my workers. I
basically want to automate things so
2007 May 15
6
Behaviour of pool_size setting
Hi,
I have backgroundrb running to decouple the execution of massive
business logic from an ActionWebservice request. The service is designed
to take some configuration parameters and fire a lot of background
workers to do the requested work. Due to performance reasons I want to
limit the number of workers to a maximum number of 30. But when I start
a configuration that requires for example