Kbase P148538: How can I view the memory statistics of an AppServer broker using JConsole?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
30/10/2009 |
|
Status: Verified
GOAL:
How can I view the memory statistics of an AppServer broker using JConsole?
GOAL:
How can I monitor memory usage of an AppServer broker using JConsole?
GOAL:
Can JConsole be used to view the current java heap size of an AppServer broker?
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.1B
OpenEdge 10.1C
FIX:
There are several JVM arguments that need to be added to the java command line invoking the AppServer broker. One way to add these arguments is to do the following:
Edit the AdminServerPlugins.properties file in your $DLC/properties directory, and add the following new Plugin Policy Group. Note that the port number is arbitrary and does not have to be 5555. You can choose any port number as long as it is not already being 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
Modify the [Plugin.AppServer] group by adding the following property:
pluginpolicy=PluginPolicy.Progress.Ubroker
When the AppServer is started either using the asbman command, Progress Explorer or OpenEdge Management/Explorer, the new jvmargs will be added that allow JConsole to view the AppServer broker process.
Refer to the documentation available for each operating system on how to run JConsole. When connecting to an agent with JConsole, the port number should match the port number used in the jvmargs line added to the AdminServerPlugins.properties file (e.g. 5555).