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

Jerry Cwiklik closed UIMA-1937.
-------------------------------

    Resolution: Fixed

The cause of the exception was an invalid proxy to a Cas Multiplier 
CasPoolMBean. A proxy was instantiated during initialization of the JMX Monitor 
but it was not properly initialized due to an invalid name used to lookup the 
MBean. The names of the colocated CM Cas Pool MBeans were changed to support 
multple CM in the same JVM. The names now contain a unique string to identify 
each instance.

> UIMA AS JMX Monitor throws javax.management.AttributeNotFoundException: No 
> such attribute: AvailableInstances
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: UIMA-1937
>                 URL: https://issues.apache.org/jira/browse/UIMA-1937
>             Project: UIMA
>          Issue Type: Bug
>          Components: Async Scaleout
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.3.1AS
>
>
> The JMX Monitor throws javax.management.AttributeNotFoundException: No such 
> attribute: AvailableInstances exception when it tries to access CM CasPool 
> MBean properties. Looks like RMI proxy is not valid when the look up is done

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

Reply via email to