[ https://issues.apache.org/jira/browse/UIMA-5136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik closed UIMA-5136. ------------------------------- Resolution: Fixed Segregated each pipeline into its own hierarchy in JMX. Modified code to use deployment specific registry for MBeans. This provides a way to manage pipeline specific MBeans. When a specific pipeline is undeployed it is now easy to remove related MBeans from the JMX registry without effecting other pipelines > UIMA-AS: the undeploy removes all MBeans from JMX > -------------------------------------------------- > > Key: UIMA-5136 > URL: https://issues.apache.org/jira/browse/UIMA-5136 > Project: UIMA > Issue Type: Bug > Components: Async Scaleout > Affects Versions: 2.8.1AS > Reporter: Jerry Cwiklik > Assignee: Jerry Cwiklik > Fix For: 2.9.0AS > > > If there are multiple pipelines deployed in the same process, an undeploy of > one of them causes all MBeans to be removed. The remaining pipeline's > statistics are destroyed in the middle of processing. > The code in question is: > Line 138 -140 in org.apache.uima.aae.jmx.JmxManager > public void destroy() throws Exception { > unregisterDomainObjects("org.apache.uima:type=ee.jms.services,*"); > } > The undeploy should only remove MBeans related to a pipeline being undeployed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)