[
https://jira.jboss.org/jira/browse/JBMESSAGING-1421?page=com.atlassian.ji...
]
Jeff Mesnil closed JBMESSAGING-1421.
------------------------------------
Resolution: Done
fixed in the trunk
I've also checked manually using our perf code that the problem Clebert reported on
the forum is no longer there.
Once the connection TTL is hit, the 2nd perfListener will receive the messages kept by the
1st killed perfListener
QueueImpl::consumer is not cleared when the socket is closed
------------------------------------------------------------
Key: JBMESSAGING-1421
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-1421
Project: JBoss Messaging
Issue Type: Bug
Reporter: Clebert Suconic
Assignee: Jeff Mesnil
Fix For: 2.0.0 Beta
When the client socket is closed, RemotingServiceImpl::connectionDestroyed is called but
nothing is activing the FailureListeners on Server Side, as a result when a client created
a consumer, the consumer will stay forever on QueueImpl.
Look at the forum thread for more details.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira