PQ62793: NODE FOR RESTART OPTION FAILS TO KILL JVM PROCESS ID OF APPSERVER THAT FAILS ON STARTUP.

A fix is available
System Management Component Cumulative Fix for 4.0.2/4.0.3/4.0.4 /4.0.5

APAR

APAR status
Closed as program error.

Error description
When customer uses xmlconfig to perform a node for restart
on a node, and that particular node has a jvm that failed
to start on startup but started succesfully afterwards, the
process id for that jvm remains after the node has been
restarted.  Customer has to perform a kill - 9 on the process
id in order for it to go away.  On Windows 2K, a reboot
is in order for the process to go away.  To recreate this
problem, rename a jar file for an ejb in an application server.
Startup that application server and it will fail due to the
Local fix
can not locate the jar.  After renaming the jar file and
then starting the ejb the appserver is fine.  The appserver
actually starts but there is an error with the ejb container
initially.  Local fix is to perform a kill -9 on the stray
java process or on NT reboot.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server 3.5 and 4.0     *
*                 users                                        *
****************************************************************
* PROBLEM DESCRIPTION: Node "stop for restart" option fails    *
*                      to kill application server jvm          *
*                      process id.                             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When using xmlconfig/wscp/admin console to perform a "node for
restart" on a node, and that particular node has a jvm that
failed to start on startup (application server initialization
failure), the process id for that jvm remains after the node
has been restarted.  Users have to perform a kill -9 on the
process id in order for it to go away.  On windows 2K, a reboot
is in order for the process to go away.
Problem conclusion
The application server process will never be stopped using the
node "stop for restart" option in any admin client once the
application server fails to start due to the application failure
or other reason.  The problem is the admin server does not
update/restore the ejbserver state in the object configuration
thus causing the stop function to fail to stop the application
server process.
Temporary fix
The testfix is available on wasdoc0\apars\PQ62793. Wait for
the customer's feedback.
Comments
APAR information
APAR numberPQ62793
Reported component nameWAS ADVANCED SU
Reported component ID5648C8402
Reported release350
StatusCLOSED PER
PENoPE
HIPERNoHIPER
Submitted date2002-07-01
Closed date2002-08-09
Last modified date2002-11-12

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:

PQ68151

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

Fix information
Fixed component nameWAS ADVANCED SU
Fixed component ID5648C8402

Applicable component levels
R350 PSYUP











Document Information

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