PQ69956: DR. ADMIN UTILIZES "LOCALHOST" AS DRADMIN HOST WHEN STARTING ADMINSERVER AND NOT THE VIRTUAL IP ADDRESS/HOST SPECIFIED. | |||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||
![]() 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 allowProblem 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 feedbacComments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
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
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.