Configuring JVM Monitoring for Windows in Apache Qpid Java Broker

To collect JVM-related metrics, the eG agent connects to the Apache Qpid Java Broker via JMX. By default, JMX support is not enabled on Apache Qpid Java Broker. However, to enable the eG agent to use JMX, the JVM tests that the eG agent runs should be configured with a JMX Remote Port - this is the port at which the JMX listens for requests from remote hosts. You need to determine the available JMX remote port to configure.

Determining the JMX Remote Port

JMX can be configured based on the availability of the port. For our assumption, the JMX is configured in port 16666. To enable JVM metrics for Apache Qpid Java Broker component, first we need to specify the binary file location (for example:installation location\bin\qpid-server.bat) and then check whether/not the JMX remote arguments are enabled (see ).

Figure 1 : Determining the JMX Remote Arguments for Windows in Apache Qpid Java Broker

By default, the JMX parameters are added. If the JMX parameters are not added, then add the following lines after “ :runCommand” in qpid-server.bat file.

set COMMAND="%JAVA_HOME%\bin\java" -Djava.rmi.server.hostname= %JAVA_VM% %JAVA_MEM% %JAVA_GC% %QPID_OPTS% %JPDA_OPTS%
%SYSTEM_PROPS% -cp "%CLASSPATH%;%MODULE_JARS%" org.apache.qpid.server.Main %QPID_ARGS%
if "%debug%" == "true" echo %CLASSPATH%;%LAUNCH_JAR%;%MODULE_JARS%
if "%debug%" == "true" echo %COMMAND%

Then restart the server with the command as

installation location\bin\qpid-server.bat