[rabbitmq-discuss] Shovel bug in 2.2.0? (fixed in 2.4.0?)

Matthew Sackman matthew at rabbitmq.com
Fri Apr 1 16:54:26 BST 2011

Hi Øyvind,

On Fri, Apr 01, 2011 at 05:51:04PM +0200, Øyvind Tjervaag wrote:
> I'm using version 2.2.0 (Erlang 14B on windows) with a shovel between two rabbit servers. When the shovel plugin looses it connection to the remote rabbit server (tested by stopping the rabbit service at the other end) the number of used Erlang processes seems to grow steadily each time the shovel tries to reconnect.
> These processes are not reclaimed when I start the remote rabbit server back up. Noticed this when it had been running for a while and rabbit stopped when reached max number of Erlang processes available.
> .. Just downloaded v 2.4.0 and without doing too much testing, this version seems to behave properly. When the shovel tries to reconnect, the Erlang process count rises by 30, but drops back by 30 before a new reconnect attempt is performed.
> Am I right in thinking there was a bug in 2.2.0 that has been fixed, or do I need to do further testing? :) Just did a 2-minute experiment...

You are correct - the bug was reported to us a while ago and has since
been fixed. I think it might have been fixed in 2.3.0/2.3.1 too, but
it's certainly fixed in 2.4.0.


More information about the rabbitmq-discuss mailing list