PQ68151: NODE FOR RESTART OPTION FAILS TO KILL JVM PROCESS ID OF APPSERVER THAT FAILS ON STARTUP. | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() 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 theLocal 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 is sysrouted FROM one or more of the following: PQ62793 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 #: PQ68151
IBM Group: Software Group
Modified date: Nov 12, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.