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, ""}

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web308

  • 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, ""}
  • via SpringSource Issue Tracker by Wei Hu (QE), 1 year ago
    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, ""}
  • via Google Groups by Matthew Ward, 1 year ago
    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@275e538e"}
  • Stack trace

    • 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, ""} at com.rabbitmq.client.QueueingConsumer.handle(QueueingConsumer.java:198) at com.rabbitmq.client.QueueingConsumer.nextDelivery(QueueingConsumer.java:214) at com.vmware.vhadoop.adaptor.rabbit.RabbitAdaptor.blockAndReceive(RabbitAdaptor.java:29) at com.vmware.vhadoop.vhm.EmbeddedVHM.start(EmbeddedVHM.java:69) at com.vmware.vhadoop.vhm.MainController.main(MainController.java:118)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 10 months ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago