[Backgroundrb-devel] Delete a busy worker
walter at katipo.co.nz
Thu Jan 3 15:40:34 EST 2008
I'm experiencing this, too. I can delete a worker after it's finished
it's finished executing a particular ask_work with :worker_method
call, but I can't "abort" the worker early if I want to interrupt
execution of ask_work.
I do call delete_worker with both the :worker and :job_key specified.
So I second Zach's problem.
On Jan 4, 2008, at 9:10 AM, Raimond Garcia wrote:
> Hmmm, check out the examples folder inside vendor/plugins/
> backgroundrb, that helped me get everything up and running with the
> new version.
> On Jan 3, 2008, at 9:03 PM, Zachary Powell wrote:
>> This worker doesn't have a key, so that makes no difference... I've
>> tried making a test method which just does sleep(60) and I can't
>> kill that either (with or without key).. Its strange, I thought it
>> worked when I first migrated over, maybe it doesn't work since 299
>> (I noticed it now saves statuses after the worker is deleted, so it
>> could be related to that perhaps - if it is a bug).
>> On 1/3/08, Raimond Garcia <voodoorai2000 at gmail.com> wrote:
>> Hi, I think there has been some changes in the arguments, the
>> following is working fine for me.
>> MiddleMan.delete_worker(:worker => :example_worker, :job_key
>> => :that_long_process)
>> On Jan 3, 2008, at 8:17 PM, Zachary Powell wrote:
>> > I thought I could delete a busy worker by calling
>> > MiddleMan.delete_worker, but doesn't seem to end. I believe this
>> > possible in 0.2, is it not in 1.0?
>> > thanks,
>> > Zach
>> > _______________________________________________
>> > Backgroundrb-devel mailing list
>> > Backgroundrb-devel at rubyforge.org
>> > http://rubyforge.org/mailman/listinfo/backgroundrb-devel
>> Backgroundrb-devel mailing list
>> Backgroundrb-devel at rubyforge.org
> Backgroundrb-devel mailing list
> Backgroundrb-devel at rubyforge.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Backgroundrb-devel