[
https://issues.jboss.org/browse/REMJMX-37?page=com.atlassian.jira.plugin....
]
Darran Lofthouse commented on REMJMX-37:
----------------------------------------
Just to clarify - the server running scenario should have been covered by REMJMX-34 -
clients are required to call close and REMJMX-34 finished off a couple of gaps where we
were handling the close correctly, my biggest concern here is the stuck threads when there
was no server running as if the client did not connect it is not natural to expect the
client to disconnect.
One related point - the messages exchanged are versioned and the protocol has not been
updated since AS 7.1.0.Final so the next release of this library should still be usable on
the client side.
defunct remoting threads left running, keeping client process alive
indefinitely.
----------------------------------------------------------------------------------
Key: REMJMX-37
URL:
https://issues.jboss.org/browse/REMJMX-37
Project: Remoting JMX
Issue Type: Bug
Components: Connection
Affects Versions: 1.0.0.GA
Reporter: Rob Stryker
Assignee: Darran Lofthouse
Priority: Critical
Fix For: 1.0.3.Final
Attachments: MyMain.java, serverRunning.stack.txt, serverStopped.stack.txt
A simple main class testing a connection to as71 over jmx will have it's process
never terminate. Remoting threads remain open.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira