[infinispan-issues] [JBoss JIRA] (ISPN-6310) Endpoints registered via CLI have wrong JMX name
Martin Gencur (JIRA)
issues at jboss.org
Thu Mar 3 03:45:00 EST 2016
Martin Gencur created ISPN-6310:
-----------------------------------
Summary: Endpoints registered via CLI have wrong JMX name
Key: ISPN-6310
URL: https://issues.jboss.org/browse/ISPN-6310
Project: Infinispan
Issue Type: Bug
Components: CLI, Server
Affects Versions: 8.2.0.CR1
Reporter: Martin Gencur
When I register second Memcached (called "memcached2") endpoint via CLI, the resulting JMX name is
{code}
jboss.datagrid-infinispan2:type=Server,name=Memcached,component=Transport
{code}
This is wrong because when the endpoint is configured in domain.xml, the resulting address is different:
{code}
jboss.datagrid-infinispan:type=Server,name=Memcached-memcached2,component=Transport
{code}
I suppose the latter name is correct because all the other Infinispan MBeans can be found under that domain (jboss.datagrid-infinispan). OTOH, when CLI is used and the second endpoint added, the new doman jboss.datagrid-infinispan2 has only a single MBean under itself, and that is the new endpoint.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the infinispan-issues
mailing list