PQ69732: ADMIN SERVER DOES NOT RECONNECT TO RUNNING APP SERVERS.

 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
When the admin and nanny process is killed and restated, the
statuses of the application server are not correct.  Here's
what's happening:
.
1. WAS node has application server Default running.
2. The admin and nanny process are killed, but Default is left
running.
3. startupServer.sh is run to restart the admin and nanny
process
4. When you run ApplicaitonServer show all for the Default
server its Current State is stopped and Desired State is
running.
5. If you enter the admin GUI its show that the Default server
is not running
.
Isn't the state information stored in the admin database and
when the admin and nanny process is restarted, shouldn't it read
the admin database and get the previous states for the Default
server?
.
If "Node startup state" is set to "RUNNING" for an app server in
the admin console, then when admin server is restarted, it does
not attempt to reconnect to the app server.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: Users of WebSphere Application Server on     *
*                 UNIX platforms.                              *
****************************************************************
* PROBLEM DESCRIPTION: Admin Server fails to connect to        *
*                      running application server.             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
This is just one of many problems associated with timing
windows in the native code library, libWsProcessManagement.so.
This particular one was associated with a race condition when
an application server terminates.  Another result could be
sudden termination of the admin server.
Problem conclusion
Closed timing window that exists when one thread is in the
function, unix_StopProcess() and another in
unix_WaitForProcessTermination().  Also took opportunity to add
a unix_doSIGSEGV() method for testing.
Temporary fix
Test fix given to customer on 13Jan03.
Comments
APAR information
APAR number PQ69732
Reported component name WEBSPHERE AE SO
Reported component ID 5630A2202
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-01-10
Closed date 2003-01-28
Last modified date 2003-01-28

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
Fixed component name WEBSPHERE AE SO
Fixed component ID 5630A2202

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 #: PQ69732
IBM Group: Software Group
Modified date: Jan 28, 2003