[
https://issues.jboss.org/browse/AS7-4822?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-4822:
---------------------------------------
I've tried to reproduce this using the given jars as well as with the jars from the
7.1.1 and 7.1.2 releases. Unfortunately, I can't. As was discussed on IRC, there were
fixes in remoting for 7.1.2 related to this sort of problem. Since I can't reproduce
this but you seem to be able to easily, if you could check whether it still happens with
7.1.2, I'd appreciate it. I'll keep experimenting with higher latency
environments, since you said you found this when working with a server on the other side
of the world.
multi-threaded client can't clean up threads
--------------------------------------------
Key: AS7-4822
URL:
https://issues.jboss.org/browse/AS7-4822
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.0.Final
Reporter: Rob Stryker
Assignee: Brian Stansberry
Attachments: AS7-4822.frozen.Main.java, AS7-4822.frozen.stacktrace
When using a multi-threaded remote management client, several threads refuse to clean up,
leaving to a deadlocked / frozen thread during a call to client.close().
Simple POJP to be attached, with stack trace. Jars on the classpath are as follows:
jboss-as-controller-client-7.1.0.Final.jar
jboss-as-protocol-7.1.0.Final.jar
jboss-dmr-1.1.1.Final.jar
jboss-logging-3.1.0.GA.jar
jboss-marshalling-1.3.9.GA.jar
jboss-remoting-3.2.2.GA.jar OR jboss-remoting-3.2.7.GA.jar
jboss-sasl-1.0.0.Final.jar
jboss-threads-2.0.0.GA.jar
xnio-api-3.0.3.GA.jar
xnio-nio-3.0.3.GA.jar
--
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