[
https://issues.apache.org/jira/browse/QPID-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14006044#comment-14006044
]
Robbie Gemmell commented on QPID-5771:
--------------------------------------
The 1.0 session etc objects in/on the connection get cleaned up within specific
1.0 connection closed() cleanup method I found was failing to unregister the
connection (its the only place that does that and it was failing to do it). By
removing the second session or the consumer you probably just took out the
particular objects causing it to throw while the connection is closing abruptly
(in the case I saw, it was trying to send something over the connection object
that was closing itself) .
Those bits should be examined themselves (that's why I'm asking Rob to review,
so he can look at it :P), but whatever actually happens in there the closed()
method should not allow the effect you observed and the change so far stops it
doing so.
> [Java broker] severed 1.0 connections can prevent clean shutdown
> ----------------------------------------------------------------
>
> Key: QPID-5771
> URL: https://issues.apache.org/jira/browse/QPID-5771
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.28
> Reporter: Gordon Sim
> Assignee: Rob Godfrey
> Fix For: 0.29
>
> Attachments: Simple.java
>
>
> ... if the connection from the attached test is killed (rather than closing
> cleanly).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
