You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <ui...@incubator.apache.org> on 2008/12/15 19:41:44 UTC

[jira] Resolved: (UIMA-1247) MBean Registration not thread-safe

     [ https://issues.apache.org/jira/browse/UIMA-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marshall Schor resolved UIMA-1247.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.3
         Assignee: Adam Lally  (was: Marshall Schor)

Adam - can you check this fix?

> 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
>             Fix For: 2.3
>
>
> 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.