[rabbitmq-discuss] RMQ Java Client - ChannelN.waitForConfirm randomly throwing exceptions

[Emanuele G]

Emanuele G wrote:
> 
> Hello,
> I am using the latest RabbitMQ java client, but while doing some perf.
> test I randomly get this exception:
> Caused by: com.rabbitmq.client.ShutdownSignalException: connection error;
> reason: {#method<connection.close>(reply-code=503,
> reply-text=COMMAND_INVALID - second 'channel.open' seen, class-id=20,
> method-id=10), null, ""}
> 	at com.rabbitmq.client.impl.ChannelN.waitForConfirms(ChannelN.java:182)
> ~[amqp-client-2.8.1.jar:na]
> 	at com.rabbitmq.client.impl.ChannelN.waitForConfirms(ChannelN.java:170)
> ~[amqp-client-2.8.1.jar:na]
> 
> Why is this happening and how can I workaround it ?
> 

I want to add that I am getting the same error this user reported in this
discussion:

http://old.nabble.com/ShutdownSignalException-second-%27channel.open%27-to33227075.html#a33227075
-- 
View this message in context: http://old.nabble.com/RMQ-Java-Client---ChannelN.waitForConfirm-randomly-throwing-exceptions-tp33544834p33544840.html
Sent from the RabbitMQ mailing list archive at Nabble.com.