[
https://issues.apache.org/jira/browse/DEFT-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Schildmeijer updated DEFT-146:
------------------------------------
Fix Version/s: 0.5.0
> JMX registration in a multi-threaded web server environment
> -----------------------------------------------------------
>
> Key: DEFT-146
> URL: https://issues.apache.org/jira/browse/DEFT-146
> Project: Deft
> Issue Type: Bug
> Priority: Minor
> Fix For: 0.5.0
>
>
> Got a lot of these (harmless) Errors when running the deft web server
> component using > 1 thread.
> 13:00:49.422 [main] ERROR org.deftserver.util.MXBeanUtil - Unable to
> register org.deftserver.io.timeout.JMXDebuggableTimeoutManager MXBean:
> javax.management.InstanceAlreadyExistsException:
> org.deftserver:type=TimeoutManager,name=JMXDebuggableTimeoutManager
> 13:00:49.422 [main] ERROR org.deftserver.util.MXBeanUtil - Unable to
> register org.deftserver.io.callback.JMXDebuggableCallbackManager MXBean:
> javax.management.InstanceAlreadyExistsException:
> org.deftserver:type=CallbackManager,name=JMXDebuggableCallbackManager
> 13:00:49.423 [main] ERROR org.deftserver.util.MXBeanUtil - Unable to
> register org.deftserver.io.IOLoop MXBean:
> javax.management.InstanceAlreadyExistsException:
> org.deftserver:type=IOLoop,name=IOLoop
> Naive solution/proposal(?): use unique names, like we do for ioloop thread
> naming
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
