[rabbitmq-discuss] Blocking Queue - Close connection by client
mklishin at gopivotal.com
Mon Apr 14 13:03:56 BST 2014
On 10 April 2014 at 10:16:49, Claire Fautsch (cfautsch at goodgamestudios.com) wrote:
> > Unfortunatelly calling the abort function instead of close,
> will show exactly the same behaviour, as there is still a flush
> at the end (I also tested this, and indeed not a solution). The
> only difference is that Exceptions/Stacktraces are ignroed.
> The only option I see so far to avoid hanging here, is to set a timeout
> to the close method.
Your observations are correct.
N.B. if you have a connection blocked, opening a new one will only help if the
new connection doesn’t publish anything. Which suggests you can separate connections
that consume and publish from the start.
Software Engineer, Pivotal/RabbitMQ
More information about the rabbitmq-discuss