[rabbitmq-discuss] RabbitMQ problem

Fri Sep 26 01:47:40 BST 2008

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi, I think I've found another bug in RabbitMQ.

Basically:
* create durable exchange and durable queue
* start a transaction
* send a couple of messages
* with the transaction still open delete the queue that was matching
* commit the transaction
* send some other messages

- -> rabbitmq will fail (but this is not the problem) with the following  
error:

=ERROR REPORT==== 25-Sep-2008::17:32:28 ===
connection <0.155.0> (running), channel 1 - error:
{commit_failed,
     [{exit,
          {noproc,{gen_server,call,[<0.169.0>,{commit,{{2,<0.161.0>}, 
36}}]}}}]}

=ERROR REPORT==== 25-Sep-2008::17:32:28 ===
Non-AMQP exit reason '{commit_failed,
                           [{exit,
                                {noproc,
                                    {gen_server,call,
                                        [<0.169.0>,
                                         {commit,{{2,<0.161.0>}, 
36}}]}}}]}'

====> Here's the error then: rabbitmq simply stops delivering messages  
and I think
it actually loses all the messages that it receives after the failing  
commit.

I don't have a usecase for this in my software (at least not yet) but
I think this thing can happen with auto_delete queues.

I tried adding code that in case of a failed commit runs the rollback  
but apparently I don't
even receive the failed commit message.

- --
Valentino Volonghi aka Dialtone
Now running MacOS X 10.5
Home Page: http://www.twisted.it
http://www.adroll.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)

iEYEARECAAYFAkjcMS0ACgkQ9Llz28widGWdJQCg4enyRR/KevS78Tku4a9NFIDM
4/YAniyLjIX4MZuDkCsWYiwQtEDnINTN
=QODa
-----END PGP SIGNATURE-----