[Backgroundrb-devel] Restarting BackgrounDRb Means Restarting Mongrel?
ian.lesperance at gmail.com
Wed Jun 18 16:09:12 EDT 2008
I am hesitant to jump onto the edge, since this is being used in a
production application. Also, since I believe I've managed to eliminate our
reason for needing to restart BackgrounDRb, it's more of an inconvenience at
Do you have plans to tag a release anytime soon, be it through Subversion or
On Mon, Jun 16, 2008 at 6:34 PM, hemant <gethemant at gmail.com> wrote:
> On Mon, Jun 16, 2008 at 11:58 PM, Ian Lesperance
> <ian.lesperance at gmail.com> wrote:
> > I've noticed that I can never just restart BackgrounDRb by itself. As
> > as I do that, Mongrel can no longer pass requests off to it. The only
> > to get it working again is by restarting Mongrel. As annoying as that
> > be, I suppose I could justify it to myself, since BackgrounDRb is
> > essentially resetting itself and its connections.
> > But what seems odd is that Mongrel (or, rather, MiddleMan) doesn't seem
> > notice that it's requests aren't getting through. That is, no errors are
> > ever thrown. The requests just die silently.
> > Is this the expected behavior? Shouldn't MiddleMan notice that it's
> > connection to BackgrounDRb just got severed? Or am I missing something?
> Are you running svn version of the plugin?
> In git version essentially a new clean connection is made for each
> request and hence you shouldn't see above mentioned problem. Please
> try upgrading and let me know, how it went?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Backgroundrb-devel