[
https://issues.apache.org/jira/browse/QPID-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Ritchie resolved QPID-372.
---------------------------------
Resolution: Fixed
Broker didn't actually close connection.. only the channel. Which caused a
close-close-ok-close loop.
Completed: At revision: 509172
> Broker doesn't wait for a ChannelClose-OK in response to a Close which can
> cause the connection to be closed.
> -------------------------------------------------------------------------------------------------------------
>
> Key: QPID-372
> URL: https://issues.apache.org/jira/browse/QPID-372
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker, Java Client
> Reporter: Martin Ritchie
> Assigned To: Martin Ritchie
>
> If a channel close occurs during a process on the client that requires
> multiple AMQP methods and subsequent methods rely on that channel then the
> broker will close the connection as an error occured on the channel and so
> must close.
> Nothing further can happen on that channel and a new channel with the same
> identifier cannot be created until the OK method is received.
> pool-1-thread-4 2007-02-15 12:21:44,171 ERROR
> [qpid.server.protocol.AMQProtocolSession] Closing channel due to: Invalid
> routing key [error code 323]
> pool-1-thread-4 2007-02-15 12:21:44,187 ERROR
> [qpid.server.protocol.AMQProtocolSession] Closing connection due to: No such
> channel: 1 [error code 504]
> pool-1-thread-4 2007-02-15 12:21:44,187 ERROR
> [qpid.server.protocol.AMQProtocolSession] Closing connection due to: No such
> channel: 1 [error code 504]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
