You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org> on 2009/07/09 17:30:14 UTC

[jira] Created: (UIMA-1429) Generate unique JMX name for every UIMA AS client instance

Generate unique JMX name for every UIMA AS client instance
----------------------------------------------------------

                 Key: UIMA-1429
                 URL: https://issues.apache.org/jira/browse/UIMA-1429
             Project: UIMA
          Issue Type: Bug
          Components: Async Scaleout
            Reporter: Jerry Cwiklik
            Assignee: Jerry Cwiklik


When an application creates a second instance of a UIMA AS client in the same JVM, an exception is thrown in the initialize() method. Only the first instance initializes correctly. This exception is thrown when the second instance attempts to register a JMX MBean (to expose client side stats) with a JMX Server. This is due to the fact that both instances try to register the MBean using the same ObjectName. Modify the client code to make the name unique before registering with JMX.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (UIMA-1429) Generate unique JMX name for every UIMA AS client instance

Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/UIMA-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik updated UIMA-1429:
--------------------------------

    Fix Version/s: 2.3AS

> Generate unique JMX name for every UIMA AS client instance
> ----------------------------------------------------------
>
>                 Key: UIMA-1429
>                 URL: https://issues.apache.org/jira/browse/UIMA-1429
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.3AS
>
>
> When an application creates a second instance of a UIMA AS client in the same JVM, an exception is thrown in the initialize() method. Only the first instance initializes correctly. This exception is thrown when the second instance attempts to register a JMX MBean (to expose client side stats) with a JMX Server. This is due to the fact that both instances try to register the MBean using the same ObjectName. Modify the client code to make the name unique before registering with JMX.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (UIMA-1429) Generate unique JMX name for every UIMA AS client instance

Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
    [ https://issues.apache.org/jira/browse/UIMA-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12729315#action_12729315 ] 

Jerry Cwiklik commented on UIMA-1429:
-------------------------------------

Fixed the client code to add a unique id (UUID) to the MBean name before it is registered with JMX Server

> Generate unique JMX name for every UIMA AS client instance
> ----------------------------------------------------------
>
>                 Key: UIMA-1429
>                 URL: https://issues.apache.org/jira/browse/UIMA-1429
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>
> When an application creates a second instance of a UIMA AS client in the same JVM, an exception is thrown in the initialize() method. Only the first instance initializes correctly. This exception is thrown when the second instance attempts to register a JMX MBean (to expose client side stats) with a JMX Server. This is due to the fact that both instances try to register the MBean using the same ObjectName. Modify the client code to make the name unique before registering with JMX.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (UIMA-1429) Generate unique JMX name for every UIMA AS client instance

Posted by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/UIMA-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jerry Cwiklik closed UIMA-1429.
-------------------------------

    Resolution: Fixed

Assign unique name to client's MBean name

> Generate unique JMX name for every UIMA AS client instance
> ----------------------------------------------------------
>
>                 Key: UIMA-1429
>                 URL: https://issues.apache.org/jira/browse/UIMA-1429
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>
> When an application creates a second instance of a UIMA AS client in the same JVM, an exception is thrown in the initialize() method. Only the first instance initializes correctly. This exception is thrown when the second instance attempts to register a JMX MBean (to expose client side stats) with a JMX Server. This is due to the fact that both instances try to register the MBean using the same ObjectName. Modify the client code to make the name unique before registering with JMX.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.