You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2011/02/04 17:03:28 UTC
[jira] Reopened: (QPID-3021) the Session and Connector actors
should be set for events occurring on 0-10 connections
[ https://issues.apache.org/jira/browse/QPID-3021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell reopened QPID-3021:
----------------------------------
Assignee: Robbie Gemmell (was: Andrew Kennedy)
In working on QPID-3029 it became clear that the 0-10 client/broker was not making use of channel number 0 when infact they could/should be doing so, unlike when using 0-9 where channel 0 represents the connection itself.
As a result of this, it became clear that enabling that to happen would mean the current check used as reason to set the ConnectionActor for 0-10 connection events such as ConnectionClose is not sufficient (whereby the lack of a particular session being present is used as cause). The connection controls may actually be transmitted using any channel number, which might have an attached session.
Setting of the connection actor for Connection Control events should be updated to be independent of the channel number of the event.
> the Session and Connector actors should be set for events occurring on 0-10 connections
> ---------------------------------------------------------------------------------------
>
> Key: QPID-3021
> URL: https://issues.apache.org/jira/browse/QPID-3021
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.8, 0.9
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Fix For: 0.9
>
>
> When addressing QPID-3014 it was noticed that the Session and Connector actors were not being set appropriately when processing events arriving on 0-10 connections. As a result, logging such as session close and connection close do not properly convey the associated LogActor, and instead reported either the actor for the wrong connection that was previously left on the CurrentAActor stack, or jsut the default Broker actor supplied when the stack is empty.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org