cannot start JCP - error "Address already in use: bind"' at ''.
search cancel

cannot start JCP - error "Address already in use: bind"' at ''.


Article ID: 129466


Updated On:


CA Automic Workload Automation - Automation Engine CA Automic One Automation


Get below error message when starting JCP:
20190305/145817.418 - 35               RESTEASY002210: Adding provider singleton from Application class
20190305/145817.502 - 35               Jetty: Started o.e.j.s.ServletContextHandler@2a796c62{/,null,AVAILABLE}
20190305/145817.503 - 35     U00045014 Exception ' "Address already in use: bind"' at ''.



20191221/042444.037 - 26     U00045014 Exception ' "Failed to bind to"' at 'org.eclipse.jetty.server.ServerConnector.openAcceptChannel():346'.
20191221/042444.038 - 26     U00045015 The previous error was caused by ' "Address already in use"' at ''.
20191221/042444.039 - 26     U00003620 Routine '' forces trace because of error.
20191221/042444.085 - 26     U00003450 The TRACE file was opened with the switches '0000000000000000'.


JCP seems to started but ended right after.



Component: AAUTEN


The REST port is occupied. In this example, port 8088 was occupied by other software.
Change this port to other free port or stop the software which uses the 8088 port will fix this issue.

20190305/145753.466 - 19               [REST]
20190305/145753.466 - 19               port=8088

This can also be caused by running the ZDU on a system with a single server and JCP - if this is the case, it should be okay to stop the "old" JCP and start up the "new" one.

In the case of a problem with ZDU, this can be resolved by either:

  • Updating the current ucsrv.ini to have the port= setting in the [REST] ini file to have more than one port, like:


  • or having the ucsrv.ini file for the target system (12.3.9) have a different port than the base system (12.3.2), like: