WCC UI not working : java.net.BindException: Address already in use (Bind failed)
search cancel

WCC UI not working : java.net.BindException: Address already in use (Bind failed)

book

Article ID: 258176

calendar_today

Updated On:

Products

CA Workload Automation AE

Issue/Introduction

We are getting below error not able to see jobs and console also not loading


CAUAJM_E_10527 Timed out waiting for response from the CA WAAE Application Server: [host:9000]
CAUAJM_E_50033 Error initializing tx subsystem:  CAUAJM_E_10062 Failed to get initial configuration from CA WAAE Application Server(s).


E139012 Autosys error response: The AutoSys application server timed out.
E131003 Error loading the job:E180010 Could not establish a connection to CA Workload Automation AE; invalid server context.

WCC UI went down or did not come up

 

Environment

Release : 11.4

Cause

INFO   | jvm 1    | 2023/01/20 02:58:49 |      101 | Jan 20, 2023 2:58:49 AM org.apache.catalina.startup.Catalina start
INFO   | jvm 1    | 2023/01/20 02:58:49 |      101 | INFO: Server startup in 102668 ms
INFO   | jvm 1    | 2023/01/20 02:58:49 |      101 | Jan 20, 2023 2:58:49 AM org.apache.catalina.core.StandardServer await
INFO   | jvm 1    | 2023/01/20 02:58:49 |      101 | SEVERE: StandardServer.await: create[localhost:8005]:
INFO   | jvm 1    | 2023/01/20 02:58:49 |      101 | java.net.BindException: Address already in use (Bind failed)
INFO   | jvm 1    | 2023/01/20 02:58:49 |      101 |    at java.net.PlainSocketImpl.socketBind(Native Method)
INFO   | jvm 1    | 2023/01/20 02:58:49 |      101 |    at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
INFO   | jvm 1    | 2023/01/20 02:58:49 |      101 |    at java.net.ServerSocket.bind(ServerSocket.java:375)

The above error message indicate that:

the HTTP connector could not start, because the server already opened that port. Your browser/client/whatever sent the request to the admin port , the server does not understand HTTP requests.

Indicating that connections on either client side or server side connections in hung mode that rejects requests come from end part.

In these scenarios we shutdown services for both parties which WCC and Autosys Application Server.

Resolution

Part of remediation, we stopped application server and WCC services for both primary and secondary that helped in establishing new/fresh connections for http requests and responses.