Bug 1210176 - Infinispan MBeans are available under two JMX domains
Summary: Infinispan MBeans are available under two JMX domains
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ER3
: 6.5.0
Assignee: Galder Zamarreño
QA Contact: Martin Gencur
Depends On:
TreeView+ depends on / blocked
Reported: 2015-04-09 06:18 UTC by Martin Gencur
Modified: 2019-03-22 07:41 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-06-23 12:24:40 UTC
Type: Bug

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-5401 0 Major Resolved Align server and embedded exposed management properties 2018-07-24 05:16:32 UTC

Description Martin Gencur 2015-04-09 06:18:47 UTC
This is related to BZ1193276 where a customer is getting errors when accessing Infinispan MBeans under wrong JMX domain.
The MBeans are by default available under:
1) jboss.as
2) jboss.infinispan

Option 2) is correct. Option 1) should be removed as it is confusing and does not work correctly.

Comment 2 Tristan Tarrant 2015-04-22 12:24:35 UTC
We can't remove either:

1. jboss.as is created by the server subsystem machinery
2. jboss.infinispan are symmetric to the ones created by embedded mode

However some attributes in 2 are missing compared to 1 and we should add them for completeness:
e.g. isCoordinator()

Comment 3 Martin Gencur 2015-04-22 13:42:04 UTC
Renamed the issue to better reflect the goal - adding the missing MBeans/attributes.

Comment 4 JBoss JIRA Server 2015-04-22 14:57:14 UTC
Galder Zamarreño <galder.zamarreno> updated the status of jira ISPN-5401 to Coding In Progress

Comment 6 Martin Gencur 2015-04-30 09:27:38 UTC
When I start ER3 JDG server, I can't find isCoordinator and coordinatorAddress on cache manager MBeans under jboss.infinispan JMX domain. There's probably something missing.

Comment 7 Martin Gencur 2015-04-30 09:50:45 UTC
Sorry, my bad. I was accidentally testing ER2. 

It works fine with ER3.

Note You need to log in before you can comment on or make changes to this bug.