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 number | PQ62494 | Reported component name | WAS ADVANCED SU | Reported component ID | 5648C8402 | Reported release | 350 | Status | CLOSED PER | PE | NoPE | HIPER | NoHIPER | Submitted date | 2002-06-20 | Closed date | 2002-08-20 | Last modified date | 2002-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 APAR is sysrouted TO one or more of the following:Modules/Macros
|
Fix information |
Fixed component name | WAS ADVANCED SU | Fixed component ID | 5648C8402 |
Applicable component levels | R350 PSN | UP |
|