[rabbitmq-discuss] Problem after upgrading to 2.3.1

Thu Feb 24 14:27:08 GMT 2011

Hi,

In my company we are running rabbitmq 1.7.0 over windows.
I am trying now to upgrade the rabbitmq to the current 2.3.1 version and
encountered a problem.
Generally, after upgrade and no code change in the application side I am
getting the following exception

reply-code=406,reply-text=PRECONDITION_FAILED - unknown delivery tag
1,class-id=60,method-id=80),null,""}

First, I will Explain how my system works and then my exception.
when App A wants to send an async message to App B and receive an answer,
this is the algorythm:

1. App A generate a unique ID and puts it in the message object
2. Then App A subscribes to a new Queue with both the queue name and routing
key equals to the new uuid.
3. App B open the message, do some calculations and return the result to the
channel with the routingkey that it received.
4. App A gets the answer and close the queue.

So far everything went really well in 1.7.0. what went wrong in 2.3.1?

When Application A does basicPublish() application B immidiately throws
CentralExceptionHandler

com.rabbitmq.client.ShutdownSignalException: channel error; reason:
{#method<channel.close>(reply-code=406,reply-text=PRECONDITION_FAILED -
unknown delivery tag 1,class-id=60,method-id=80),null,""}
at com.rabbitmq.client.impl.ChannelN.processAsync(ChannelN.java:191)
at
com.rabbitmq.client.impl.AMQChannel.handleCompleteInboundCommand(AMQChannel.java:159)
at com.rabbitmq.client.impl.AMQChannel.handleFrame(AMQChannel.java:110)
at
com.rabbitmq.client.impl.AMQConnection$MainLoop.run(AMQConnection.java:438)
Caused by: com.rabbitmq.client.ShutdownSignalException: channel error;
reason:
{#method<channel.close>(reply-code=406,reply-text=PRECONDITION_FAILED -
unknown delivery tag 1,class-id=60,method-id=80),null,""}

Any one got some idea?
Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110224/bb4c09f3/attachment.htm>