[
https://jira.jboss.org/jira/browse/JBAS-3381?page=com.atlassian.jira.plug...
]
Dheeraj Uppalapati commented on JBAS-3381:
------------------------------------------
I'm not sure whether I'm posting my issue at the right place, but I'm facing
the same issue when I'm trying to access the JMX console on the production server. But
I'm able to access JMX console on the development. Can you please tell me how can I
resolve this issue (OR) where should I start to resolve this issue.
18:27:40,126 INFO [Server] Starting JBoss (MX MicroKernel)...
18:27:40,126 INFO [Server] Release ID: JBoss [Zion] 4.0.5.GA (build: CVSTag=Branch_4_0
date=200610162339)
18:27:40,141 INFO [Server] Home Dir: C:\jboss-4.0.5.GA
18:27:40,141 INFO [Server] Home URL: file:/C:/jboss-4.0.5.GA/
18:27:40,141 INFO [Server] Patch URL: null
18:27:40,141 INFO [Server] Server Name: default
18:27:40,141 INFO [Server] Server Home Dir: C:\jboss-4.0.5.GA\server\default
18:27:40,141 INFO [Server] Server Home URL: file:/C:/jboss-4.0.5.GA/server/default/
18:27:40,141 INFO [Server] Server Log Dir: C:\jboss-4.0.5.GA\server\default\log
18:27:40,141 INFO [Server] Server Temp Dir: C:\jboss-4.0.5.GA\server\default\tmp
18:27:40,141 INFO [Server] Root Deployment Filename: jboss-service.xml
18:27:40,782 INFO [ServerInfo] Java version: 1.5.0_22,Sun Microsystems Inc.
18:27:40,782 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_22-b03,Sun
Microsystems Inc.
18:27:40,782 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
The
----
Key: JBAS-3381
URL:
https://jira.jboss.org/jira/browse/JBAS-3381
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMX
Affects Versions: JBossAS-4.0.4.GA
Environment: [sstark@sstark bin]$ $JAVA_HOME/bin/java -version
java version "1.6.0-beta2"
Java(TM) SE Runtime Environment (build 1.6.0-beta2-b86)
Java HotSpot(TM) Client VM (build 1.6.0-beta2-b86, mixed mode, sharing)
Reporter: Scott M Stark
Assignee: Scott M Stark
Fix For: JBossAS-4.0.5.CR1, JBossAS-5.0.0.Beta1
When bridging the jboss MBeanServer and the jdk platform MBeanServer using the
javax.management.builder.initial and jboss.platform.mbeanserver settings:
JAVA_OPTS="$JAVA_OPTS
-Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl"
JAVA_OPTS="$JAVA_OPTS -Djboss.platform.mbeanserver"
the following error can be seen tyring to display the mbeans on the jmx-console:
13:41:31,812 ERROR [[HtmlAdaptor]] Servlet.service() for servlet HtmlAdaptor threw
exception
javax.management.InstanceNotFoundException: com.sun.management:type=HotSpotDiagnostic is
not registered.
at
org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:523)
at org.jboss.mx.server.MBeanServerImpl.getMBeanInfo(MBeanServerImpl.java:666)
at
org.jboss.system.server.jmx.LazyMBeanServer.getMBeanInfo(LazyMBeanServer.java:308)
at org.jboss.jmx.adaptor.control.Server.getDomainData(Server.java:78)
at
org.jboss.jmx.adaptor.html.HtmlAdaptorServlet.displayMBeans(HtmlAdaptorServlet.java:181)
The problem is that the selection of the correct MBeanServer is not considering all of
the possible domains. Currently only domains prefixed with "java" are considered
to belong to the platform MBeanServer.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira