[
https://jira.jboss.org/jira/browse/JOPR-15?page=com.atlassian.jira.plugin...
]
Charles Crouch commented on JOPR-15:
------------------------------------
To reproduce I put the following in run.conf
JAVA_OPTS="$JAVA_OPTS -Xms512m -Xmx512m"
JAVA_OPTS="$JAVA_OPTS -Dsun.rmi.dgc.client.gcInterval=3600000"
JAVA_OPTS="$JAVA_OPTS -Dsun.rmi.dgc.server.gcInterval=3600000"
JAVA_OPTS="$JAVA_OPTS -XX:PermSize=192m -XX:MaxPermSize=192m"
JAVA_OPTS="$JAVA_OPTS -XX:NewSize=128m -XX:MaxNewSize=128m"
JAVA_OPTS="$JAVA_OPTS -XX:+DisableExplicitGC"
JAVA_OPTS="$JAVA_OPTS -XX:+UseConcMarkSweepGC"
JAVA_OPTS="$JAVA_OPTS -XX:+UseParNewGC"
JAVA_OPTS="$JAVA_OPTS -XX:ThreadStackSize=128"
JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.port=3001"
JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.ssl=false"
JAVA_OPTS="$JAVA_OPTS
-Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl"
JAVA_OPTS="$JAVA_OPTS -Djboss.platform.mbeanserver"
JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.authenticate=false"
With jmx remoting enabled JBAS JVM servers are found as sibling
resources rather than child resources
-----------------------------------------------------------------------------------------------------
Key: JOPR-15
URL:
https://jira.jboss.org/jira/browse/JOPR-15
Project: Jopr
Issue Type: Bug
Components: Plugin - JBoss AS 4
Affects Versions: 2.1
Reporter: Charles Crouch
Attachments: screenshot-1.jpg
Normally when you start a JBAS instance with -Djboss.platform.mbeanserver the JON agent
will discover the JVM MBeanServer running underneath the JBAS instance as a *child*
resource of the JBAS Server. However if you have jmx remoting enabled then the JVM
resource is found as *sibling* of the JBAS resource.
--
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