My Oracle Support Banner

java.net.BindException: Address already in use: JVM_Bind (Java SE6 1.6.0_51+ and JDK1.7u25+) on Microsoft Windows (Doc ID 1932828.1)

Last updated on JULY 26, 2018

Applies to:

Oracle WebLogic Server - Version 10.3 to 12.1.3.0.0
Java SE JDK and JRE - Version 6 to 7 [Release 6 to 7]
Microsoft Windows (32-bit)
Microsoft Windows x64 (64-bit)

Symptoms

An error java.net.BindException: Address already in use: JVM_Bind appears in server logs when using Java SE6 1.6.0_51+ and JDK1.7u25+, but the address:port combination is not being used. In some cases, you can see that the JVM continues to RUN (usually using any port type (SSL/non-SSL)) and in other cases ,you can see the JVM shut itself down (typically when the domain-wide administration port is used).

  1. Using any non-SSL or SSL port (JVM gives error but continue to run). Error Snippet:
    <Error> <Server> <MACHINE> <AdminServer> <DynamicListenThread[Default[2]]> <> <> <> <1411984210148> <BEA-002606> <Unable to create a server socket for listening on channel "Default[2]". The address 0:0:0:0:0:0:0:1 might be incorrect or another process is using port 7001: java.net.BindException: Address already in use: JVM_Bind.> <=======FALSE
    <Notice> <WebLogicServer> <MACHINE> <AdminServer> <main> <> <> <> <1411984210319> <BEA-000360> <Server started in RUNNING mode>
  2. Using the domain-wide administration port (JVM shutdown). Error Snippet:
    <Error> <Server> <MACHINE> <AdminServer> <DynamicJSSEListenThread[DefaultAdministration[2]]> <> <> <> <1411984449405> <BEA-002606> <Unable to create a server socket for listening on channel "DefaultAdministration[2]". The address 0:0:0:0:0:0:0:1 might be incorrect or another process is using port <ADMINPORT>: java.net.BindException: Address already in use: JVM_Bind.>  <=============================================FALSE
    <Notice> <Server> <MACHINE> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1411984449514> <BEA-002612> <Channel "DefaultAdministration[2]" listening on 0:0:0:0:0:0:0:1:<ADMINPORT> did not start did not start properly.>
     <Critical> <WebLogicServer> <MACHINE> <AdminServer> <main> <> <> <> <1411984449514> <BEA-000362> <Server failed. Reason: Failed to start admin channel DefaultAdministration[admin][2]>
     <Notice> <WebLogicServer> <MACHINE> <AdminServer> <main> <> <> <> <1411984449514> <BEA-000365> <Server state changed to FAILED>
     <Error> <WebLogicServer> <MACHINE> <AdminServer> <main> <> <> <> <1411984449514> <BEA-000383> <A critical service failed. The server will shut itself down>

Changes

There has been a change in the Networking API Implementation on Windows platforms.

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.