[rabbitmq-discuss] Reconnect to RabbitMQ broker

Simon MacMullen simon at rabbitmq.com
Thu Mar 15 11:07:24 GMT 2012


On 15/03/12 02:46, Matthew Ward wrote:
> As expected, Connection Refused exceptions are thrown (and caught) while
> rabbitmq is off. As soon as I bring the server back online, it throws
> ShutDownSignalExceptions:
>
> com.rabbitmq.client.ShutdownSignalException: connection error; reason:
> {#method<connection.close>(reply-code=320, reply-text=CONNECTION_FORCED
> - broker forced connection closure with reason 'shutdown', class-id=0,
> method-id=0), null, "[B at 275e538e"}
> at com.rabbitmq.client.QueueingConsumer.handle(QueueingConsumer.java:198)
> at
> com.rabbitmq.client.QueueingConsumer.nextDelivery(QueueingConsumer.java:214)

Unfortunately there's a bug in the 2.7.1 Java client that obscures the 
real error message here. The server logs should tell you more about what 
the server is objecting to.

Cheers, Simon


-- 
Simon MacMullen
RabbitMQ, VMware


More information about the rabbitmq-discuss mailing list