Starting Application Server with additional JMX Agent is not supported.
J2SE 1.4.x, 5.0, or later can be configured on the Application Server.
An integral feature of J2SE 5.0 platform is the ability to start a JMX agent.
This is activated when you explicitly set system properties at the server
startup.
Example values include:
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 Virtual Machine.
An undesirable side-effect of this is that the administration functions are
affected adversely, and the Application Server administration Console and
command—line interface may produce unexpected results. The problem is
that there are some conflicts between the built in jmx-connector server
and the new jmx-connector server.
Solution
If using jconsole (or any other JMX-compliant client),
consider reusing the standard JMX Connector Server that is started with Application
Server startup.
When the server starts up, a line similar to the one shown below appears
in the server.log. You can connect to the JMXService URL
specified there and perform the same management/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 Administration Guide.
|