PQ83796: WPC PROCESSES THAT WERE ALREADY RUNNING BEFORE THE QUEUEMANAGER WAS STOPPED, CONTINUE TO RUN. | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description After stopping and restarting the QueueManager the system doesn't work any more. The symptom is, that processes that were already running before the QueueManager was stopped, continue to run, but it is not possible to start new long-running processes. The same problem may also occur if an Application server runs for a long time and a cached connection to the QueueManager becomes invalid for whatever reason. The symptom seen in the trace is com.ibm.bpe.api.UnexpectedFailureException: BPEA0010E: Unexpected exception during execution. javax.jms.IllegalStateException: Connection invalidatedLocal fix Problem summary **************************************************************** * USERS AFFECTED: All users of the Process Choreographer * * function of WebSphere Application Server * * Enterprise 5.0.2 * **************************************************************** * PROBLEM DESCRIPTION: If the connection to the QueueManager * * is lost (e.g. by shutdown of * * QueueManager) and then reestablished, * * processes that were started before the * * loss of the connection continue to run, * * but it is not possible to start new * * long running processes. * * The same problem may also occur if an * * Application server runs for a long * * time and a cached connection to the * * QueueManager becomes invalid for * * whatever reason. * * The symptom seen in the system log is * * com.ibm.bpe.api.UnexpectedFailure * * Exception: BPEA0010E: Unexpected * * exception during execution. * * javax.jms.IllegalStateException: * * Connection invalidated * **************************************************************** * RECOMMENDATION: * **************************************************************** If the connection to the QueueManager is lost (e.g. by shutdown of QueueManager) and then reestablished, processes that were started before the loss of the connection continue to run, but it is not possible to start new long running processes. The same problem may also occur if an Application server runs for a long time and a cached connection to the QueueManager becomes invalid for whatever reason. The symptom seen in the system log is com.ibm.bpe.api. UnexpectedFailure Exception: BPEA0010E: Unexpected exception during execution. javax.jms.IllegalStateException: Connection invalidatedProblem conclusion Applying the fix for this APAR will resolve this problem.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ83796
IBM Group: Software Group
Modified date: Apr 26, 2004
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.