The jmxremote port is used by the bwengine even though the JMX properties are disabled.

The jmxremote port is used by the bwengine even though the JMX properties are disabled.

book

Article ID: KB0085226

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix BusinessWorks -
Not Applicable -

Description

Description:
When using JMX monitoring and setting the following properties:

Jmx.Enabled=false
java.property.com.sun.management.jmxremote=false
java.property.com.sun.management.jmxremote.port=10100
java.property.com.sun.management.jmxremote.authenticate=false
java.property.com.sun.management.jmxremote.ssl=false

Although JMX and remoteJmx properties are disabled, the bwengine still uses the JMX port number in the netstat result:


 netstat -ano | grep 10100
 TCP    0.0.0.0:10100          0.0.0.0:0              LISTENING       2688
 TCP    [::]:10100             [::]:0                 LISTENING       2688


Symptoms:

When setting the JMX properties to "false" and starting the application (another application with the custom engine properties set to "default" values is already deployed), the following error is thrown:


Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 10100; nested exception is: java.net.BindException: Address already in use.
Cause:
The is due to defect: BW-16320.

Resolution

Delete the JMX related properties in the bwengine.xml file.

-OR-

Before deploying an application, change the JMX port number to a different port for each application. This can be done from the Admin GUI.

Issue/Introduction

The jmxremote port is used by the bwengine even though the JMX properties are disabled.

Additional Information

TIBCO ActiveMatrix BusinessWorks->Administration->Appendix B Monitoring the BusinessWorks Engine Using JMX : Enabling JMX Support

Powered by Wolken Software