You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (JIRA)" <ji...@apache.org> on 2014/10/30 18:09:34 UTC
[jira] [Resolved] (QPID-6192) Broker model closes exchanges/queues
before connections
[ https://issues.apache.org/jira/browse/QPID-6192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy resolved QPID-6192.
------------------------------
Resolution: Fixed
The changes look good
> Broker model closes exchanges/queues before connections
> -------------------------------------------------------
>
> Key: QPID-6192
> URL: https://issues.apache.org/jira/browse/QPID-6192
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.30
> Reporter: Keith Wall
> Assignee: Alex Rudyy
> Fix For: 0.31
>
>
> The Broker Model closes virtualhost children exchanges/queues before connections. This allows for the possibility that work done on the connection can fail in surprising ways, for instance, a basic.publish can fail as the exchange object can no longer be found.
> An instance of this problem is described next.
> bq. In our test case, we have a publishing thread, publishing as fast as it can. The broker is shutdown gracefully. Sometimes we see a channel.close AMQException "Unknown exchange name" in response to a basic.publish. Adding logging shows that the Broker is closing and deregistering the exchange before the connection is closed, meaning that the client has the opportunity to get another basic.publish over the wire, to which the broker will respond with the channel.close. This closes the client's session, meaning after failover, the user is left with a connection with a closed session.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org