PQ62494: ADMIN SERVER SHOULD RECONNECT TO RUNNING APP SERVERS RUNNING AND/OR STARTED

Fixes are available
WebSphere Application Server Version 4.0 Fix Pack 5 (Version 4.0.5)
System Management Component Cumulative Fix for 4.0.2/4.0.3/4.0.4 /4.0.5
PQ87712; 4.0.5-4.0.7: Application Server processes become orphans after restart

APAR

APAR status
Closed as program error.

Error description
The expected behavior for the AdminServer is to reconnect to
appservers that are already running . There should not be any
new process created.
But currently, Websphere AdminServer always considers a START
as NEW WAS start and goes ahead and starts the appservers.
(WAS has to consult with admin DB to decide if it has to start
appserver or not ). There is a flag which will tell the
adminserver if that is a restart, which is never set, since the
startupServer script is used to start the Adminserver, Websphere
considers it as a normal start and creates a new appserver
process.
Local fix
NA
Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users.      *
****************************************************************
* PROBLEM DESCRIPTION: If admin server is restarted, it fails  *
*                      to connect to running app servers.      *
*                      This may result in multiple copies of   *
*                      app servers running simultaneously.     *
*                                                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Several problems were corrected so that admin server can
successfully check for existence of and connect to
running app servers.  To have this behavior, it is required
that the user add the following to line to admin.config:

forceReconnectProp=com.ibm.ejs.sm.adminServer.forceReconnect
that the user add the following to line to admin.config:forceReconnectProp=com.ibm.ejs.sm.adminServer.forceReconnect
Problem conclusion
Test fix sent to customer and feedback was reported good.
Code dropped for inclusion in future updates.
Line item 1720 LIDB1720 defect 148585
Temporary fix
Test fix sent to L2 on 24Jun02 - awaiting feedback
Comments
APAR information
APAR numberPQ62494
Reported component nameWAS ADVANCED SU
Reported component ID5648C8402
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2002-06-20
Closed date2002-08-20
Last modified date2002-11-01

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:


Modules/Macros
ADMINSVR
APAR is sysrouted TO one or more of the following:Modules/Macros

Fix information
Fixed component nameWAS ADVANCED SU
Fixed component ID5648C8402

Applicable component levels
R350 PSNUP











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Software version: 350
Reference #: PQ62494
IBM Group: Software Group
Modified date: 2002-11-01