PQ81871: IF THE PROCESS INSTANTIATION FAILS, THE PROCESS IS LEFT IN A STATE RUNNING WHILE ALL ACTIVITIES ARE IN STATE INACTIVE | |||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description During failover testing we noticed the following: If the process instantiation fails (MQ on zOS is down), the process is left in a state RUNNING while all activities are in state INACTIVE and there is no message on the INT queue (continue connector) to kick off the first activity - this is a "should-not-occur".Local fix Problem summary **************************************************************** * USERS AFFECTED: Customers using Process Choreographer in * * the WebSphere Application Server 5.0.2 * * Enterprise Edition * **************************************************************** * PROBLEM DESCRIPTION: When an instance of an interruptible * * process (macroflow) is created and * * there is a problem with sending * * messages, for example, messages * * cannot be put onto an internally-used * * queue, then the process instance is * * created but the follow-on messages * * are not sent. This leaves the process * * instance in an inconsistent state. * * Its starting activities are never * * scheduled but remain inactive. You * * can terminate the process instance. * **************************************************************** * RECOMMENDATION: * **************************************************************** When an instance of an interruptible process (macroflow) is created and there is a problem with sending messages, for example, messages cannot be put onto an internally-used queue, then the process instance is created but the follow-on messages are not sent. This leaves the process instance in an inconsistent state. Its starting activities are never scheduled but remain inactive. You can terminate the process instance.Problem conclusion A flag was being incorrectly set for DB updates during transaction for the creation of the process instance. After encountering JMS errors, a commit of the transaction rather than a rollback was made since the flag indicated no DB updatesTemporary 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 > Enterprise Edition (EE)
Operating system(s):
Software version: 00W
Software edition:
Reference #: PQ81871
IBM Group: Software Group
Modified date: Mar 5, 2004
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.