[JBoss JIRA] (ISPN-10899) Server transport and executor metrics are not unregistered on stop
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-10899?page=com.atlassian.jira.plugin... ]
Dan Berindei updated ISPN-10899:
--------------------------------
Status: Open (was: New)
> Server transport and executor metrics are not unregistered on stop
> ------------------------------------------------------------------
>
> Key: ISPN-10899
> URL: https://issues.jboss.org/browse/ISPN-10899
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 10.0.1.Final
> Reporter: Dan Berindei
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 10.1.0.Beta1
>
>
> Server transport and executor are registered in JMX with {{CacheManagerJmxRegistration.registerExternalMBean()}}, which also registers them in the metrics registry.
> But they're unregistered with {{JmxUtil.unregisterMBean()}}, which doesn't unregister them from the metrics registry.
> We really need to remove {{JmxUtil}} and only use the {{xJmxRegistration}} components everywhere except the client.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months
[JBoss JIRA] (ISPN-10899) Server transport and executor metrics are not unregistered on stop
by Dan Berindei (Jira)
Dan Berindei created ISPN-10899:
-----------------------------------
Summary: Server transport and executor metrics are not unregistered on stop
Key: ISPN-10899
URL: https://issues.jboss.org/browse/ISPN-10899
Project: Infinispan
Issue Type: Bug
Components: Server
Affects Versions: 10.0.1.Final
Reporter: Dan Berindei
Assignee: Nistor Adrian
Fix For: 10.1.0.Beta1
Server transport and executor are registered in JMX with {{CacheManagerJmxRegistration.registerExternalMBean()}}, which also registers them in the metrics registry.
But they're unregistered with {{JmxUtil.unregisterMBean()}}, which doesn't unregister them from the metrics registry.
We really need to remove {{JmxUtil}} and only use the {{xJmxRegistration}} components everywhere except the client.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 6 months