[Backgroundrb-devel] Stopping DRb after using BackgrounDRb::MiddleManDRbObject.init

Jacob Robbins jrobbins at cmj.com
Fri Jan 19 11:15:11 EST 2007

   Is there more than one drb connection from each mongrel? I would 
think that each rails app would have one drb connection to each of the 
backgroundrb servers that it has accessed.

   I'm not quite understanding what the problem is, is it that you have 
N mongrels and M backgroundrb serves and it's too much to have N*M drb 
connections? Or is it that each mongrel is constantly making more new 
drb connections instead of reusing the existing ones?


Michael D'Auria wrote:
> You need to clean up your workers yourself, so toss in a self.delete 
> inside of the do_work method to have the worker clean up after itself or 
> you can perform a delete on the worker on the outside using it's id.
> .: Michael :.
> On 1/19/07, *Robert Bjarnason* <robert.bjarnason at gmail.com 
> <mailto:robert.bjarnason at gmail.com>> wrote:
>     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
>     _______________________________________________
>     Backgroundrb-devel mailing list
>     Backgroundrb-devel at rubyforge.org
>     <mailto:Backgroundrb-devel at rubyforge.org>
>     http://rubyforge.org/mailman/listinfo/backgroundrb-devel
> ------------------------------------------------------------------------
> _______________________________________________
> Backgroundrb-devel mailing list
> Backgroundrb-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/backgroundrb-devel

More information about the Backgroundrb-devel mailing list