JMX Port Conflict between NAC and NES in Nolio Release Automation

Products

• CA Release Automation - Release Operations Center (Nolio)

Issue/Introduction

When accessing the JMX Console the "noliocenter:type=info" is missing, which is needed to help find a stuck process.

Cause

This issue can occur if the Nolio Automation Center (NAC) and Nolio Execution Server (NES) are installed in different locations (e.g., separate drives or non-standard paths) but are configured to use the same JMX port.

In such configurations, a port conflict prevents the management services from correctly identifying and clearing process locks, leading to the system incorrectly reporting that a previous process is still running.

Resolution

To resolve this conflict, the JMX port for one of the components must be changed to a unique value.

Step 1: Identify the Port Conflict
Review the configuration files for both NAC and NES to check for duplicate port assignments (default is often 20203 depending on the version).

Step 2: Modify the Configuration

• Navigate to the installation directory of the component you wish to modify.
• Locate the configuration file (typically distributed.properties).
• Update the JMX port property to a unique, unused port on the server.

Step 3: Restart Services

Validation
Once services are restarted, log in to the JMX Console and verify that the "noliocenter:type=info" is now available.