Symptom

When starting the Content Update Service (CUS), the following error appears in the wrapper.log file:

Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 1099; nested exception is:
java.net.BindException: Address already in use: bind

This prevents the service from starting properly.

Cause

The error indicates that port 1099, the default port used by Java for JMX monitoring, is already occupied by another process on the system.

Resolution

Change the JMX Port in the wrapper.conf Configuration File

1. Open the file wrapper.conf located in the conf/ folder of your CUS installation.

2. Locate the following line:

wrapper.java.additional.15=-Dcom.sun.management.jmxremote.port=1099

3. Change the port number to an unused one, e.g. 1199:

wrapper.java.additional.15=-Dcom.sun.management.jmxremote.port=1199

4. Save the file and restart the Content Update Service.

Note:

Changing the JMX port only affects remote Java process monitoring and does not interfere with the core update functionality of the Content Update Service.
It is safe to change this port as long as the new value is unused.
 

Reference:

• Content Update Service - PTV xServer 2 Documentation

• Java JMX Documentation (Oracle)

Related articles

PTV xServer: Content Update Service connection issues - How to Resolve Timeout Errors When Connecting to LDS in Content