[rabbitmq-discuss] dropped messages on low volume

Matthew Sackman matthew at lshift.net
Wed Jul 1 15:57:34 BST 2009

Hi Joel,

On Wed, Jul 01, 2009 at 03:39:14PM +0100, Joel Reymont wrote:
> On Jul 1, 2009, at 1:03 PM, Matthew Sackman wrote:
> >Could you thus rework this to use tx_select, publish and tx_commit?

Ok, we've had some more thoughts here about this, and basically, we
don't think you should need transactions (which aren't in the lib_amqp
module as you've found (and I'd forgotten)). The teardown that you're
doing is synchronous and will force everything out, so there is no risk
of messages getting stuck in the client. Thus don't worry about
transactions, and leave the teardown in.

We're wondering whether you're using the same channel or connection for
all of your clients? If so, that would be bad as as soon as one of them
closes, the other messages will not get through - teardown shuts both
the channel and the connection.

Could you send us the complete code so that we can reproduce the


More information about the rabbitmq-discuss mailing list