jmx-dev Bug with jmxmp

[shanliang]

Fabrice,

I remember that it was intended to create that thread as non-daemon, in 
order to keep your JVM alive in case that there is no any other thread. 
So you have to stop your JMXMP server before stopping the JVM

Shanliang


Fabrice Bacchella wrote:
> I found a bug with the current implementation of jmxmp. The javax.management.remote.generic.GenericConnectorServer create an anonymous, non-daemon thread.
>
> So it can prevent a jvm to stop.
>
> I found the code at :
> http://grepcode.com/file/repo1.maven.org/maven2/org.jvnet.opendmk/jmxremote_optional/1.0_01-ea/javax/management/remote/generic/GenericConnectorServer.java#GenericConnectorServer
>
> Look at the private class Receiver, it as no custom constructor, and it usage is :
> 289    // start to receive clients
> 290    receiver = new Receiver();
> 291    receiver.start();
> 292}
>
> Is there any bug trafic or official repository for that ?
>
> https://opendmk.java.net is almost dead.