[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-1618) Connection.close should be synchronous
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1618?page=com.atlassian.ji...
]
Tim Fox commented on JBMESSAGING-1618:
--------------------------------------
Comment this is now solved for an invm connection
(ReplicationAwareJMSServerControlWrapperTest::testListRemoteAddresses uses INVM transport)
but remains to
be solved for netty.
With netty the channel disconnected event can come in *after* the call to close the
channel has completed on the client side.
Connection.close should be synchronous
--------------------------------------
Key: JBMESSAGING-1618
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1618
Project: JBoss Messaging
Issue Type: Bug
Reporter: Clebert Suconic
Assignee: Tim Fox
Fix For: 2.0.0 Beta
This is related to
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=154639
When connection.close() is called, the server needs some time before releasing the
connection.
There is a FIXME block on
ReplicationAwareJMSServerControlWrapperTest::testListRemoteAddresses for this:
// FIXME: Closing a connection should be Synchronous
// Remove this loop block when
https://jira.jboss.org/jira/browse/JBMESSAGING-1618 is done
long timeout = System.currentTimeMillis() + 5000;
while (timeout > System.currentTimeMillis() &&
liveServerControl.listRemoteAddresses().length != 0)
{
Thread.sleep(10);
}
--
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