PPMBroker RMI port 23793 reused by cloned app services
search cancel

PPMBroker RMI port 23793 reused by cloned app services


Article ID: 268294


Updated On:


Clarity PPM SaaS Clarity PPM On Premise


After ppmbroker was added, the logic to increment the port for any cloned app service does no longer work correctly and leads to duplicate rmiPort


  1. Install a new Clarity system
  2. Start the services app, bg, nsa, beacon
  3. Now open the properties.xml
  4. Note the rmiPort for ppmbroker is 23793
  5. Now in command prompt run:
    • service clone app
    • service deploy start app2

Expected Results:  The new service to use rmiPort 23794 when automatically added. If you add more app clones you will notice they always add +1 to the port.

Actual Results: The cloned app2 service gets added with 23793 as well as the one used by ppmbroker, and although it starts, it does not correctly start so it cannot be used, error in logs

2023/06/20 08:09:31.466 | SEVERE: Failed to create server shutdown socket on address [localhost] and port [23793] (base port [23793] and offset [0])
2023/06/20 08:09:31.466 | java.net.BindException: Address already in use: NET_Bind
2023/06/20 08:09:31.466 |     at java.base/java.net.PlainSocketImpl.bind0(Native Method)
2023/06/20 08:09:31.466 |     at java.base/java.net.PlainSocketImpl.socketBind(PlainSocketImpl.java:132)
2023/06/20 08:09:31.466 |     at java.base/java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:452)
2023/06/20 08:09:31.466 |     at java.base/java.net.ServerSocket.bind(ServerSocket.java:395)
2023/06/20 08:09:31.466 |     at java.base/java.net.ServerSocket.<init>(ServerSocket.java:257)


Release : 16.1.1, 16.1.2


Workaround: Manually edit the properties.xml file after adding the service and before deploying it

This is DE70465, fixed in 16.1.3