WebSphere v4.0.x Admin Server fails to established a DrAdmin port.
 Technote (FAQ)
 
Problem
Admin Server is not able start. The following error is seen in the tracefile:

[4/18/03 10:24:46:293 EDT] 76024492 ORBRas W com.ibm.CORBA.iiop.Util Util P=885727:O=0:CT JORB0012: Pass by reference has been set to: true (NoLocalCopies = true)
[4/18/03 10:24:52:193 EDT] 76024492 DrAdminServer I WSVR0054E: Failed to create a server socket, the port 0 maybe in use: The socket name is not available on this system.
java.lang.NullPointerException
at com.ibm.ejs.sm.util.debug.DrAdminServer$2.run(DrAdminServer.java:350)
at java.security.AccessController.doPrivileged(Native Method)
at com.ibm.ejs.sm.util.debug.DrAdminServer.listen(DrAdminServer.java:347)
at com.ibm.ejs.sm.util.debug.DrAdminServer$ServerRunner.run(DrAdminServer.java:243)
 
Cause
The localhost is set to an incorrect value. To check this you can ping the localhost and you should see a different IP address return.
 
Solution
Options 1: Localhost Definition

Ensure the localhost can be resovled.

1. Try pinging the localhost, if your ping response shows a different IP, other than your localhost then this is where the problem lies.

2. Edit your /etc/host (UNIX platforms) or your \WINNT\system32\drivers\etc\host (Windows platforms) file and look for to see you configuration:


127.0.0.1 loopback localhost
15.12.4.11 machinename.fun.companyname.com machinename

In one situation, the customer was pinging the localhost and it was pointing to a fully qualified server name rather the name of the local system.

This problem was specified in SM cumulative Fix's readme and stated that DrAdmin utilizes “localhost” as the DrAdmin host when starting adminserver. This means that the machine must be able to resolve the localhost.

Ensure the hosts file includes the localhost. If you updated this file you will need to issue a restart of the admin server, which will resolve the issue with establishing a DrAdmin port.

Options 2: Static Port for DrAdmin

The second option is to assign a static port for DrAdmin to use to talk with the Admin Server.

1. Edit the <was_root>/bin/admin.config file to reflect following

# AdminServer's DrAdmin port
com.ibm.ejs.sm.adminServer.diagThreadPort=<Port#>

example:
# AdminServer's DrAdmin port
com.ibm.ejs.sm.adminServer.diagThreadPort=6789

NOTE: Ensure you are using a port that's not in use by another program to avoid conflicts.

2. Restart WebSphere admin server.

 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Servlet Engine/Web Container
Operating system(s): HP-UX
Software version: 4.0
Software edition:
Reference #: 1138228
IBM Group: Software Group
Modified date: Sep 12, 2003