Respected Contributor.
Respected Contributor.

(OO) Support Tip: splitJoinTrigger found in BLOCKED state

The splitJoin trigger has been found in a BLOCKED/ERROR state leading to multi instance flows not being completed or OO_SUSPENDED_EXECUTION backlog increases to abnormal values. The multi Instance flow completes the multi instance lanes but never transitions out to next step (in this case ‘resolved’) so it hangs in a constant ‘running’ state. This issue was found in OO versions 10.0, 10.02, 10.20, and 10.21.

This is a known issue and defect QCCR8C24579 splitJoinTrigger found in BLOCKED state. Please see the following KM document published on the SSO: https://softwaresupport.hp.com/group/softwaresupport/search-result/-/facetsearch/document/KM01010517

A hot fix has been created for this issue for OO version 10.22.

Workaround in place:

Manually update the splitJoinTrigger to WAITING by running the SQL below against the OO database:

update [dbName].[dbo].[OO_TRIGGERS] set TRIGGER_STATE='WAITING' where TRIGGER_NAME='splitJoinTrigger'

Please contact Technical Support if you have any other questions or would like a hot fix. Thank you.

Labels (1)
Tags (1)
0 Replies
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.