Application Server fails to start with "Error [125] in bind() call!" in native log
 Technote (troubleshooting)
 
Problem(Abstract)
An application server fails to start using the administrative console or the startServer script and no SystemOut.log or SystemErr.log are produced. Below are the error messages seen in the log files produced:

startServer.log:
AdminTool A ADMU3011E: Server launched but failed initialization. Server log files should contain failure information.

native_stdout.log:
FATAL ERROR in native method: No transports initialized

native_stderr.log:
Error [125] in bind() call!
err:: Address already in use
Socket transport failed to init.
Transport dt_socket failed to initialize, rc = -1.
 
Cause
The problem is a port conflict where the application server requires a port in use for debugging purposes. Following is a method for determining what port is causing the conflict:
*.7777 *.* 0 0 24576 0 LISTEN

Indicating that the conflicting port is 7777.
 
Resolving the problem
There are two solutions to resolve this issue:
  1. Disable debug mode.

  2. Change the dt_socket address.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s): Windows
Software version: 5.1.1
Software edition:
Reference #: 1170384
IBM Group: Software Group
Modified date: Aug 16, 2004