Feedback
Did this article resolve your question/issue?

   

Article

How to view the memory statistics of a Broker java process using JConsole?

Information

 
TitleHow to view the memory statistics of a Broker java process using JConsole?
URL NameP148538
Article Number000139431
EnvironmentProduct: OpenEdge
Version: 10.1B, 10.1C, 10.2x, 11.x
OS: All Supported Operating Systems
Other: AppServer
Question/Problem Description
How to view memory statistics of an Broker java process using JConsole?
How can I monitor memory usage of an AppServer broker using JConsole?
Can JConsole be used to view the current java heap size of an OpenEdge Broker's java process?
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution

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.
Workaround
Notes
Last Modified Date11/20/2020 7:30 AM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.