In Supplements If Orchestration Plan Changes Order Not Flowing Properly
(Doc ID 2255918.1)
Last updated on MARCH 27, 2019
Applies to:
Oracle Communications Order and Service Management - Version 7.2.2 and laterInformation in this document applies to any platform.
Symptoms
During supplements if orchestration plan changes then the order is not flowing properly.
In initial order we have an orchestration plan like function (in following sequence) A , B , D, E, G, and initial order is waiting in function 'D'. And then we submit a supplement, where the orchestration plan gets changed like function (in following sequence) A, B, C, D, E, F, G. After completing function 'D' order does not process properly
ERROR
----------------------
oracle.communications.ordermanagement.orchestration.execution.OrchestrationExecutionException: Error in retreiveing compensation plan:
at oracle.communications.ordermanagement.orchestration.execution.impl.a.getCompensationItems(Unknown Source)
at oracle.communications.ordermanagement.compensation.impl.b.filterStartReadyComponents(Unknown Source)
at oracle.communications.ordermanagement.orchestration.execution.impl.e.b(Unknown Source)
at oracle.communications.ordermanagement.orchestration.execution.impl.e.a(Unknown Source)
at oracle.communications.ordermanagement.orchestration.execution.provider.jms.impl.OrchestrationDependenciesMDB.onLocalMessage(Unknown Source)
at oracle.communications.ordermanagement.cluster.message.a.a(Unknown Source)
at oracle.communications.ordermanagement.cluster.message.impl.a.a(Unknown Source)
at oracle.communications.ordermanagement.cluster.message.impl.a.a(Unknown Source)
at oracle.communications.ordermanagement.cluster.impl.a.a(Unknown Source)
at oracle.communications.ordermanagement.cluster.message.ClusterMessageHandlerBean.onMessage(Unknown Source)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:583)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:486)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:388)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4659)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4345)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3821)
at weblogic.
Cause
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
Symptoms |
Cause |
Solution |
References |