[
https://issues.apache.org/jira/browse/UIMA-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654892#action_12654892
]
Adam Lally commented on UIMA-1247:
----------------------------------
This is what gets logged:
WARNING: JMX failiure: Failed to register MBean.
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.uima.internal.util.JmxMBeanAgent.registerMBean(JmxMBeanAgent.java:70)
at
org.apache.uima.analysis_engine.impl.AnalysisEngineImplBase.initialize(AnalysisEngineImplBase.java:134)
Caused By: javax.management.InstanceAlreadyExistsException
at
com.sun.jmx.mbeanserver.RepositorySupport.addMBean(RepositorySupport.java:452)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1410)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:936)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:337)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:497)
> MBean Registration not thread-safe
> ----------------------------------
>
> Key: UIMA-1247
> URL: https://issues.apache.org/jira/browse/UIMA-1247
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Affects Versions: 2.2.2
> Reporter: Adam Lally
> Assignee: Adam Lally
> Priority: Minor
>
> If you create multiple instances of the same Analysis Engine simultaneously
> in different threads, it often results in WARNING messages being written to
> the log file about failed JMX MBean registration. These don't cause the AE
> to fail, but the messages are disconcerting, especially since they contain
> the entire stack trace. When logging is going to the console these messages
> can be mistaken for serious errors.
> At the very least the warning should not contain the stack trace so it
> doesn't look as threatening. Better would be to fix the MBean registration
> so it does not encounter these problems.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
