PQ69956: DR. ADMIN UTILIZES "LOCALHOST" AS DRADMIN HOST WHEN STARTING ADMINSERVER AND NOT THE VIRTUAL IP ADDRESS/HOST SPECIFIED.

 Fixes are available

4.0.6: WebSphere Application Server Version 4.0 Fix Pack 6
System Management Component Cumulative Fix for 4.0.2/4.0.3/4.0.4 /4.0.5



APAR status
Closed as program error.

Error description
According to the current design, the DrAdminServer (Trace
Server) always uses the primay host name ("localhost") as
default trace server host (DrAdmin host), but it allows the
users to allocate a different port for DrAdmin by specifying
"com.ibm.ejs.sm.adminServer.diagThreadPort"
in admin.config.  The trace server host in admin server should
be configurable, but currently there is no diagThreadHostname
attribute defined in admin server configuration properties.
Level 3 system management dev(Amy Lin) will add the property
"com.ibm.ejs.sm.adminServer.diagThreadHostname" into admin
server configuration properties, so the users are able to change
DrAdmin host in admin.config.
.
2nd Issue addressed by this apar:
com.ibm.ejs.sm.adminServer.bootstrapHost property is not working
It is a bug in the admin server code that does not allow users
to set the
bootstrapHost (com.ibm.ejs.sm.adminServer.bootstrapHost) in
admin.config.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: For WebSphere Application Server 4.0 users   *
****************************************************************
* PROBLEM DESCRIPTION: Dr. Admin utilizes "localhost" as       *
*                      DrAdmin host when starting              *
*                      adminserver and not the virtual IP      *
*                      address/host specified                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
First problem:
According to the current 4.0 design, the DrAdminServer
(TraceServer) always uses the primary host name ("localhost")
as default trace server host (DrAdmin host), but it allows users
to allocate a different port for DrAdmin by specifying
"com.ibm.ejs.sm.adminServer.diagThreadPort" in admin.config.
The trace server host in admin server should be configurable,
but currently there is no diagThreadHostName attribute defined
in admin server configuration properties.
Second problem:
com.ibm.ejs.sm.adminServer.bootstrapHost property is not
working. It is a bug in the admin server code that did not allow
Problem conclusion
Introduced the new admin server configuration property
"com.ibm.ejs.sm.adminServer.diagThreadHostname" in
AdminServer.java and AdminServerConfigConstants.java that
allows users to specify different host name for DrAdminServer.
Modified the function validateArgs() in AdminServer.java to
allow users to specify different bootstrap host name
(com.ibm.ejs.sm.adminServer.bootstrapHost) in admin.config.
Temporary fix
The test fix has sent to the customer and is waiting for feedbac
Comments
APAR information
APAR number PQ69956
Reported component name WEBSPHERE AE AI
Reported component ID 5630A2200
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-01-16
Closed date 2003-03-03
Last modified date 2003-03-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
ADMINSVR          

SRLS

Fix information

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ69956
IBM Group: Software Group
Modified date: Mar 3, 2003