subimage at gmail.com
Sat Jan 26 00:14:34 EST 2008
'ps -ef | grep worker' on your box. If you find there are a bunch hanging
around - there's your problem. I'm running an ooold version of BDRB (0.2.1),
and I have to kill the workers from rails, or call 'exit!' at the bottom of
my do_work method to get things behaving properly.
You might be encountering something similar. Not sure what the latest and
greatest method of achieving this is...TTL perhaps anyone?
On Jan 25, 2008 8:56 PM, Meech <meechman at gmail.com> wrote:
> I'm checking out backgroundrb for a calculation process I estimate will
> take 2-3 minutes and be ran on-demand only via Rails. Very easy and slick.
> But I have a question.
> The connections never close, if I do a netstat they just keep piling up.
> Do I need to do some housekeeping somewhere? I noticed the @
> connection.close statements are commented out in favor of a # FIXME type
> Even if I store read_from_bdrb in an intermediate variable, call @
> connection.close then return, they still sit in a CLOSE_WAIT status
> forever -- long, long after mongrel has cleaned up.
> I'm not a communications guy, so if I'm doing something wrong, let me
> Backgroundrb-devel mailing list
> Backgroundrb-devel at rubyforge.org
seth at subimage interactive
Cashboard - Estimates, invoices, and time tracking software - for free!
Substruct - Open source RoR e-commerce software.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Backgroundrb-devel