Requirement Processing - Unique Constraint Violation On Insert Into AsEntityLock
(Doc ID 2629459.1)
Last updated on JANUARY 16, 2020
Applies to:Oracle Insurance Policy Administration J2EE - Version 184.108.40.206 and later
Information in this document applies to any platform.
On : 220.127.116.11 version, General
Whenever multiple requirements are processing on a policy simultaneously, there are risks of contention. In the case of using the ProcessActivities business rule with the EntityLock functionality enabled, this can result in an unexpected requirement failure and interruption of the policy processing flow. This is most likely to occur in production scenarios when new applications are submitted via external interface any many new, unprocessed requirements are added to a policy as part of that process.
The system should either:
1 - handle concurrency gracefully by allowing parallel process to wait for contended locks.
2 - prevent parallel requirement processing against the same policy in the way that activity processing is segmented - 1 thread per policy processing entities sequentially for that policy.
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