cannot start JCP - error "Address already in use: bind"' at 'sun.nio.ch.Net.bind0()'.

book

Article ID: 129466

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Get below error message when starting JCP:
==============================================
20190305/145817.418 - 35               RESTEASY002210: Adding provider singleton com.automic.rest.provider.FileSyncExceptionMapper from Application class com.automic.rest.RestApplication
20190305/145817.502 - 35               Jetty: Started [email protected]{/,null,AVAILABLE}
20190305/145817.503 - 35     U00045014 Exception 'java.net.BindException: "Address already in use: bind"' at 'sun.nio.ch.Net.bind0()'.
​​​==============================================

or

​​​==============================================

20191221/042444.037 - 26     U00045014 Exception 'java.io.IOException: "Failed to bind to 0.0.0.0/0.0.0.0:8088"' at 'org.eclipse.jetty.server.ServerConnector.openAcceptChannel():346'.
20191221/042444.038 - 26     U00045015 The previous error was caused by 'java.net.BindException: "Address already in use"' at 'sun.nio.ch.Net.bind0()'.
20191221/042444.039 - 26     U00003620 Routine 'com.automic.rest.server.RestServerComponent' 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.

 

Environment

Release:
Component: AAUTEN

Resolution

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.