Starting Application Server With Additional JMX Agent Not Supported (ID 6200011)

J2SE 1.4., 5.0, and compatible versions can be configured on the Application Server. An integral feature of the J2SE 5.0 platform is the ability to start a JMX agent. This agent is activated when you explicitly set system properties at the server startup.

Example values include the following:

name="com.sun.management.jmxremote" value="true"
name="com.sun.management.jmxremote.port" value="9999"
name="com.sun.management.jmxremote.authenticate" value="false"
name="com.sun.management.jmxremote.ssl" value="false"

After configuring JMX properties and starting the server, a new jmx-connector server is started within the Application Server VM. An undesirable side-effect of this is that the administration functions are affected adversely, and the Application Server administration GUI and CLI might produce unexpected results. These results are caused by some conflicts between the built-in jmx-connector server and the new jmx-connector server.

Solution

If using jconsole or any other JMXcompliant client, consider reusing the standard JMX Connector Server that is started atApplication Server startup.

When the server starts, a line similar to the one shown in the next paragraph appears in the server.log. You can connect to the JMXServiceURL specified there and perform the same management and configuration operations after successfully providing the credentials, for example:

[#|2004-11-24T17:49:08.203-0800|INFO|sun-appserver-ee8.1|javax.enterprise.
system.tools.admin|_ThreadID=10;|ADM1501: Here is the JMXServiceURL for the 
JMXConnectorServer: [service:jmx:rmi:///jndi/rmi://hostname:8686/management/
rmi-jmx-connector]. This is where the remote administrative clients should 
connect using the JSR 160 JMX Connectors.|#]

For more information, refer to the Sun Java System Application Server 8.2 Administration Guide.