You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Gordon Sim (JIRA)" <qp...@incubator.apache.org> on 2009/04/08 12:10:12 UTC
[jira] Resolved: (QPID-1785) Race condition in closing session due
to exception
[ https://issues.apache.org/jira/browse/QPID-1785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gordon Sim resolved QPID-1785.
------------------------------
Resolution: Fixed
Fixed as r762312 on 0.5 branch and as r763163 on trunk.
QPID-1789 tracks the logically incorrect design whereby a session going out of scope is treated as detached by client but server is not informed.
> Race condition in closing session due to exception
> --------------------------------------------------
>
> Key: QPID-1785
> URL: https://issues.apache.org/jira/browse/QPID-1785
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
> Affects Versions: M4
> Reporter: Gordon Sim
> Assignee: Gordon Sim
>
> If a Session object goes out of scope, the ConnectionImpl will throw a
> FramingErrorException for any frames received on the correspodning channel.
> This is in itself incorrect as the broker may not have ever been sent a detach.
> However it only causes a real problem when a session is closed due to an
> exception. In this case the client receives an execution.exception command
> followed by a session.detach control. If the session goes out of scope between
> the processing of these two, the handling of the detach causes a
> FramingErrorException which causes the client to close the connection thus
> destroying all other active sessions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org