[
http://jira.jboss.com/jira/browse/JBREM-746?page=comments#action_12390087 ]
Ron Sigal commented on JBREM-746:
---------------------------------
Further commentary from John Mazzitelli:
The problem is the remoting stuff doesn't adhere to the JBAS JMX environment properly
in all cases - specifically, it doesn't work if you tell JBossAS to use the platform
MBeanServer. The remoting war still wants to use the "jboss" MbeanServer.
need to be able to tell ServerInvokerServlet to use the platform
MBean server
-----------------------------------------------------------------------------
Key: JBREM-746
URL:
http://jira.jboss.com/jira/browse/JBREM-746
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto)
Reporter: John Mazzitelli
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto)
Attachments: ServerInvokerServlet.patch
Right now, ServerInvokerServlet assumes the MBeanServer where it can find the server
invoker is the JBoss MBeanServer.
See the comments in ServerInvokerServlet.getMBeanServer()
It would be nice to be able to tell it to not use the MBeanServer whose default domain is
"jboss", but rather we should be able to tell it (via servlet init params)
either:
a) the name of the MBeanServer's default domain (in case I want to use my own, not
the jboss one)
or
b) a flag to indicate it should use the Java5 platform MBeanServer
(java.lang.management.ManagementFactory.getPlatformMBeanServer())
Workaround is for customers to write their own subclass of ServerInvokerServlet, override
the getMBeanServer method to find the appropriate one.
--
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