TRANSACTIONS GETTING TIMED OUT. CONCRETE ACTIVATION STATUS NOT CONFIRMED.
Last updated on AUGUST 13, 2013
Applies to:Oracle Communications IP Service Activator - Version: 5.2.4 to 5.2.4
Information in this document applies to any platform.
Problem descriptionThe following behavior occurred when multiple orders that included multiple IPSA transactions are pushed rapidly through the API . Though the state of the concrete(s) corresponding to the timed out transaction is 'Installed', the Provisioning Status is 'Timedout'. The State of the transaction is 'Committed', and the Activation State of the concrete(s) is 'Pending'.
The following fault is raised in IPSA corresponding to the transaction:
"xxx:xxxx - Concrete activation state set to timedout where activation status was not confirmed".
Policy server errorxxxxxxxx-xxxxx1|0010|TRC2|ConcreteActivationStatusCache::timeoutTransactions:
timed out 1 transactions
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms