BindException: Address Already In Use When Using Many GlassFish Server Clusters And Instances On a Single Mach
Last updated on APRIL 16, 2018
Applies to:Oracle GlassFish Server - Version 2.1 and later
Information in this document applies to any platform.
***Checked for relevance on 2-Nov-2013***
This problem could be seen while a GlassFish Server cluster restarts, where a few instances fail to startup with 'BindException: Address already in use' as shown below:
[#|2011-09-27T12:54:25.088+0200|SEVERE|sun-appserver2.1.1|javax.enterprise.resource.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;_ThreadName=main;all interfaces;33842;;_RequestID=2c2b1c42-d70c-4838-b55b-613d45226989;|"IOP00410216: (COMM_FAILURE) Unable to create IIOP listener on the specified host/port: all interfaces/33842"
Caused by: java.net.BindException: Address already in use
The more GlassFish Server clusters and instances are configured per single machine, the more likely it is to may be affected by this symptom due to the huge number of service ports being utilized per instance.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms