WebLogic Server Fails to Bind to SSL Port with Error "java.net.BindException: Address already in use" After Deploying New Application Version
(Doc ID 2665033.1)
Last updated on OCTOBER 01, 2021
Applies to:Oracle WebLogic Server - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
WebLogic server is unable to bind to SSL port after deploying the new version of application. It works fine with the old application code.
Observed below errors from the server log:
When WebLogic server is down, no sockets observed on the SSL port 7002.
While server is starting, noticed that there is a socket opened on the port 7002 like below, where as server listen address is set to machine's IP address xxx.xxx.xxx.xxx.
When configured WebLogic server to use next available port for its SSL (Ex: 7003), the server starts fine and binds to this new port.
New version of application code is deployed to WebLogic server.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document