[rabbitmq-discuss] Problem after upgrading to 2.3.1

Sun Feb 27 09:54:49 GMT 2011

well , thank you for your quick response.
Well, it seemed fine when I tried to do it all in my local computer (two
apps and rabbit)
but when I upgraded the clients in the production environment (whoops) the
clients threw the following exception:
(side note: I did not change any property (socket,port etc ) in the client
side. so i am guessing firewall is not an option because everything worked
with the former version of rabbit - 1.7.0.  )

com.rabbitmq.client.ShutdownSignalException: connection error; reason:
java.net.SocketException: Connection reset
at com.rabbitmq.client.impl.AMQConnection.shutdown(AMQConnection.java:588)
at
com.rabbitmq.client.impl.AMQConnection$MainLoop.run(AMQConnection.java:454)
Caused by: com.rabbitmq.client.ShutdownSignalException: connection error;
reason: java.net.SocketException: Connection reset
... 2 more
Caused by: java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at java.io.DataInputStream.readUnsignedByte(Unknown Source)
at com.rabbitmq.client.impl.Frame.readFrom(Frame.java:117)
at
com.rabbitmq.client.impl.SocketFrameHandler.readFrame(SocketFrameHandler.java:151)
at com.rabbitmq.client.impl.AMQConnection.readFrame(AMQConnection.java:379)
at
com.rabbitmq.client.impl.AMQConnection$MainLoop.run(AMQConnection.java:420)

Thank you

On Fri, Feb 25, 2011 at 1:46 PM, Matthias Radestock
<matthias at rabbitmq.com>wrote:

> On 24/02/11 15:48, mysurf mail wrote:
>
>> What I basically see is that we start listening on the receiving
>> app (subscriber)  as follows:
>>
>>             boolean durable = false;
>>             final boolean mandatory = true;
>>             final boolean immediate = true;
>>             channel.exchangeDeclare(exchangeName, "direct", durable,
>> mandatory, immediate, new HashMap<String, Object>());
>>             channel.queueDeclare(queueName, durable);
>>             channel.queueBind(queueName, exchangeName, routingKey);
>>
>>             boolean noAck = true;
>>             queueingConsumer = new QueueingConsumer(channel);
>>             channel.basicConsume(queueName, noAck, queueingConsumer);
>>
>
> So the client is consuming in noAck/autoAck mode, which means it *must not*
> basicAck the messages. The error
>
>
>      > reply-code=406,reply-text=PRECONDITION_FAILED - unknown delivery tag
>>     > 1,class-id=60,method-id=80),null,""}
>>
>
> is most likely due it doing that.
>
> Regards,
>
> Matthias.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110227/b224c0d2/attachment.htm>