Failed To Acquire Exclusive Ownership Of An Order When 2 Orders Are Executing Concurrently in Cluster

Last updated on NOVEMBER 08, 2017

Applies to:

Symptoms

When sending 2 orders (Order A and Order B) concurrently, a DB plugin of Order A takes exactly 200 seconds to complete, while Order B fails before orchestration starts. There should be an inter-order dependency between Order B to Order A.

The error in the OSM log is:

### <> <> <
oracle.communications.ordermanagement.orchestration.execution.OrchestrationExecutionException: Error creating orchestration plan
…
Caused by: oracle.communications.ordermanagement.orchestration.generation.OrchestrationPlanGeneratorException: Error creating Inter-Order Dependencies
…
Caused by: com.mslv.oms.OMSException: Failed to get handler for request due to Failed to acquire exclusive ownership of order(s)[4960] from cluster member[MS1] due to Timeout while attempting to release order[4960] from local server[MS1] after 200 seconds.

com.mslv.oms.OMSException: Timeout while attempting to release order[4960] from local server[MS1] after 200 seconds.
at oracle.communications.ordermanagement.cluster.BusinessRequestBalancer.c(Unknown Source)
at oracle.communications.ordermanagement.cluster.BusinessRequestBalancer.b(Unknown Source)
at oracle.communications.ordermanagement.cluster.impl.AgentRequestBalancerImpl$1.run(Unknown Source)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.InvocationService.onInvocationRequest(InvocationService.CDB:12)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.InvocationService$InvocationRequest.run(InvocationService.CDB:1)
at com.tangosol.coherence.component.util.DaemonPool$WrapperTask.run(DaemonPool.CDB:1)
at com.tangosol.coherence.component.util.DaemonPool$WrapperTask.run(DaemonPool.CDB:32)
at com.tangosol.coherence.component.util.DaemonPool$Daemon.onNotify(DaemonPool.CDB:63)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)

Cause