Concurrent Transactions Updating Same Concrete Failing (Doc ID 946696.1)

Last updated on AUGUST 13, 2013

Applies to:

Oracle Communications IP Service Activator - Version: 5.2.4 and later   [Release: 5.2 and later ]
Information in this document applies to any platform.

Symptoms

Concurrent multiple changes on a concrete may cause all related transactions to be marked as failed in the transaction monitor with the error highlighted below. This will happen when subsequent changes occur before the transaction status is set as completed in the transaction monitor for the first transaction on the concrete . If this condition is hit, the concrete status is the only way to determine the activation status of the target concrete. Transaction status monitor is not able to report on the correct status of the concrete, forcing the user to manually verify of the target concrete status.

Steps To Reproduce:
For example, fire 4 transactions affecting the same concrete one after the other.

System generated errors if condition is hit, error in Policy server log:

20090930-082149|001a|INF2| Concrete activation status set to failed for concretes affected by active transactions: List of transaction affected


Error in the UI (one fault per transaction affected where %1% is the affected):

Concrete activation status set to failed for concretes affected by active transactions: %1%'
Concrete activation status set to failed for concretes affected by active transactions: %1%'

Changes

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms