[jboss-jira] [JBoss JIRA] Commented: (JBAS-4623) org.jboss.web.tomcat.service.session.JBossCacheCluster creates MBeanServer with incorrent domain name
[ http://jira.jboss.com/jira/browse/JBAS-4623?page=comments#action_12373552 ]
Brian Stansberry commented on JBAS-4623:
----------------------------------------
This class is not meant to be used inside JBoss AS; it's for use in standalone Tomcat.
It's also largely untested in that usage since I wrote it as a community contribution
2 1/2 years ago (i.e. before I joined JBoss/Red Hat).
A hacky fix to this hacky usage would be to only call
MBeanServerLocator.setJBoss(getMBeanServer()) if MBeanServerLocator.locateJBoss() returns
null. A better fix would be to figure out how to ensure no classes in the package need to
find the proper mbean server in this way; they just have it injected or get it from their
Container or something.
org.jboss.web.tomcat.service.session.JBossCacheCluster creates
MBeanServer with incorrent domain name
-----------------------------------------------------------------------------------------------------
Key: JBAS-4623
URL: http://jira.jboss.com/jira/browse/JBAS-4623
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-4.2.2.GA
Reporter: William DeCoste
Assigned To: Brian Stansberry
MBeanServerLocator.setJBoss(getMBeanServer()); can create an MBeanServer with domain
"DefaultDomain" and register is with MBeanServerLocator as the "jboss"
domain. This breaks MBeanServerLocator.locateJBoss().
Let me know if you see what I mean - I can fix it.
I'm looking in Branch_4_2
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira