You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robert Greig (JIRA)" <qp...@incubator.apache.org> on 2006/12/12 15:36:30 UTC
[jira] Created: (QPID-171) Closing a connection does not propagate
closed state to child objects
Closing a connection does not propagate closed state to child objects
---------------------------------------------------------------------
Key: QPID-171
URL: http://issues.apache.org/jira/browse/QPID-171
Project: Qpid
Issue Type: Bug
Reporter: Robert Greig
In BasicMessageProducer, it appears that closing a session does not make the message producer state update.
In particular, the following methods do not throw an exception:
getDeliveryMode()
getDisableMessageId()
getDisableMessageTimestamp()
getPriority()
getTimeToLive()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (QPID-171) Closing a connection does not propagate
closed state to child objects
Posted by "Robert Greig (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-171?page=all ]
Robert Greig resolved QPID-171.
-------------------------------
Fix Version/s: M2
Resolution: Fixed
Committed to svn revision 486198
> Closing a connection does not propagate closed state to child objects
> ---------------------------------------------------------------------
>
> Key: QPID-171
> URL: http://issues.apache.org/jira/browse/QPID-171
> Project: Qpid
> Issue Type: Bug
> Reporter: Robert Greig
> Assigned To: Robert Greig
> Fix For: M2
>
> Attachments: qpid-171.patch
>
>
> In BasicMessageProducer, it appears that closing a session does not make the message producer state update.
> In particular, the following methods do not throw an exception:
> getDeliveryMode()
> getDisableMessageId()
> getDisableMessageTimestamp()
> getPriority()
> getTimeToLive()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (QPID-171) Closing a connection does not propagate
closed state to child objects
Posted by "Rob Godfrey (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-171?page=all ]
Rob Godfrey updated QPID-171:
-----------------------------
Attachment: qpid-171.patch
Patch attached, with fix and unit test
> Closing a connection does not propagate closed state to child objects
> ---------------------------------------------------------------------
>
> Key: QPID-171
> URL: http://issues.apache.org/jira/browse/QPID-171
> Project: Qpid
> Issue Type: Bug
> Reporter: Robert Greig
> Assigned To: Robert Greig
> Attachments: qpid-171.patch
>
>
> In BasicMessageProducer, it appears that closing a session does not make the message producer state update.
> In particular, the following methods do not throw an exception:
> getDeliveryMode()
> getDisableMessageId()
> getDisableMessageTimestamp()
> getPriority()
> getTimeToLive()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (QPID-171) Closing a connection does not propagate
closed state to child objects
Posted by "Robert Greig (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-171?page=all ]
Robert Greig reassigned QPID-171:
---------------------------------
Assignee: Robert Greig
> Closing a connection does not propagate closed state to child objects
> ---------------------------------------------------------------------
>
> Key: QPID-171
> URL: http://issues.apache.org/jira/browse/QPID-171
> Project: Qpid
> Issue Type: Bug
> Reporter: Robert Greig
> Assigned To: Robert Greig
>
> In BasicMessageProducer, it appears that closing a session does not make the message producer state update.
> In particular, the following methods do not throw an exception:
> getDeliveryMode()
> getDisableMessageId()
> getDisableMessageTimestamp()
> getPriority()
> getTimeToLive()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (QPID-171) Closing a connection does not
propagate closed state to child objects
Posted by "Robert Greig (JIRA)" <qp...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/QPID-171?page=comments#action_12457735 ]
Robert Greig commented on QPID-171:
-----------------------------------
Being worked on by Rob Godfrey
> Closing a connection does not propagate closed state to child objects
> ---------------------------------------------------------------------
>
> Key: QPID-171
> URL: http://issues.apache.org/jira/browse/QPID-171
> Project: Qpid
> Issue Type: Bug
> Reporter: Robert Greig
> Assigned To: Robert Greig
>
> In BasicMessageProducer, it appears that closing a session does not make the message producer state update.
> In particular, the following methods do not throw an exception:
> getDeliveryMode()
> getDisableMessageId()
> getDisableMessageTimestamp()
> getPriority()
> getTimeToLive()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira