Activity Sequencing - Entity Locking Issue
(Doc ID 2178250.1)
Last updated on MARCH 07, 2018
Applies to:Oracle Insurance Policy Administration J2EE - Version 10.0.0.0 and later
Information in this document applies to any platform.
Scenario: AS1 and AS2 are two different activities having sequences.
When AS1 starts its sequence execution, sequence task acquires the lock on policy (as AS11 is on policy)
and processes all the pending activities on that policy until the last sequence activity.
In this path of execution, AS2 is picked up to get processed and AS2 also has sequence to process.
AS2's task tries to acquire the lock on the policy which is already acquired by AS1's task which causes a deadlock.
AS2 tries to lock on a policy which AS1 has and AS1 will not release the lock
until it is done with its sequence task execution which includes AS2.
And AS2 is not aware that it is in the process of AS1 which has lock so it can proceed.
Multiple activities with sequences should be able to process without deadlocks or manual intervention.
Steps to Reproduce
1. Create 2 activities with sequences and process as described in the above scenario
2. A deadlock will occur which will require manual interventions and reprocessing.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document