To monitor memory usage of an OpenEdge Broker's java process
JVM arguments need to be added to the java command line used to start the Broker. One way to add these arguments is in the AdminServerPlugins.properties file which is outlined below, where the following information uses the AppServer Broker as the example
1. Edit the DLC/properties/AdminServerPlugins.properties file
2. Add a new Plugin Policy Group.
The port number is arbitrary and does not have to be 5555. Any available port number can be configured as long as it is not used by another process:
[PluginPolicy.Progress.Ubroker]
jvmargs=-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=5555
-Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false
3. Add the new Plugin Policy Group to the AppServer Plugin
[Plugin.AppServer]
pluginpolicy=PluginPolicy.Progress.Ubroker
When the AppServer is started using either the
asbman command, or from the OpenEdge Management/Explorer Console Browser, the new jvmargs will be added to allow JConsole to view the AppServer broker process.
WARNING: The above instruction only applies to the environment with one unified broker. To enable JMX for individual brokers, refer to Article:
How to connect Jconsole to a remote AppServer?When connecting to an agent with JConsole, use the portnumber configured in the jvmargs line added to the AdminServerPlugins.properties file (e.g. 5555).
Refer to the documentation available for each operating system on how to run JConsole.
