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.
|