Recovering From a BPM Node Crash
Restarting the BPM node after a crash may sometimes fail and/or stop process work because of various reasons. This may be because some work items are missing or the BPM application changes to a ’Partially Running’ runtime state.
These problems may occur because, when a node crashes, the process is killed. However, the XA transactions may remain active and block some engine threads within the database against orphan transactions. When the node is restarted and the orphan transactions are not cleared, some of the process cannot be restarted and result in missing workitems.
Procedure
Next topic: Removing applications from a node
Previous topic: Creating a New BPM Node with TCT Causes Failures
Copyright © Cloud Software Group, Inc. All rights reserved.