Core Client Threadpool MBean registration fails when server is restarted

Question

Core Client Threadpool MBean registration fails when server is restarted

guusdk opened this issue 3 years ago · 2 comments

When this plugin is installed in a server, and that server gets restarted, the registration of the MBean that is used to monitor the 'core client threadpool' always fails.

This registration is done when the plugin initializes, and requires the socket acceptor associated to those client connections. Acceptors are started only after all plugins have started.

Answer 1 · 2021-08-04T12:54:07.000Z

Would something simpler suffice? e.g. https://github.com/igniterealtime/openfire-hazelcast-plugin/blob/master/src/java/org/jivesoftware/openfire/plugin/HazelcastPlugin.java#L48

Answer 2 · 2021-08-04T12:56:06.000Z

I don't think so, at least not reliably, as that is the exact same construct used for the thing that we're waiting on (the socket acceptors) to start initialization. I don't think we can reliably tell which one will come first.