OSM : ComponentId Setting Causes Error With Revision Order (Doc ID 1573346.1)

Last updated on OCTOBER 03, 2016

Applies to:

Oracle Communications Order and Service Management - Version 7.2.2 to 7.2.2 [Release 7.2]
Information in this document applies to any platform.
**** Currency checked on 02-02-2015*********
**** Currency checked on 03-10-2016*********

Symptoms

PROBLEM STATEMENT
=================
Scenario 1:
===========
1. The current date is “2013-03-20” which is the same as the order creation date.
2. Submit a Future Dated Order [2013-03-30T16:00:00] with a revisionnumber of 1
3. Again submit Revision with current date order[[2013-03-20T16:00:00]] and revisionnumber is 2
4. OSM Throws errors in teh task client, osmwebui and also in the admin log

<ERROR> <jboss.JBossOrderCacheManager> <ExecuteThread: '10' for queue: 'oms.web'> <Error retrievi
ng order from cache orderId[404]>
java.lang.NullPointerException
        at com.mslv.oms.handler.order.cache.jboss.c.<init>(Unknown Source)
        at com.mslv.oms.handler.order.cache.jboss.JBossOrderCacheManager.a(Unknown Source)
        at com.mslv.oms.handler.order.cache.jboss.JBossOrderCacheManager.b(Unknown Source)
        at com.mslv.oms.handler.order.cache.jboss.JBossOrderCacheManager.a(Unknown Source)
        at com.mslv.oms.handler.order.cache.jboss.JBossOrderCacheManager$2.a(Unknown Source)
        at com.mslv.oms.handler.order.cache.jboss.JBossOrderCacheManager$2.call(Unknown Source)
        at oracle.communications.ordermanagement.util.e.a(Unknown Source)
        at com.mslv.oms.handler.order.cache.jboss.JBossOrderCacheManager.a(Unknown Source)
        at com.mslv.oms.handler.order.cache.jboss.JBossOrderCacheManager.a(Unknown Source)
        at com.mslv.oms.handler.order.cache.AbstractOrderCacheManager.a(Unknown Source)
        at com.mslv.oms.handler.order.cache.AbstractOrderCacheManager.a(Unknown Source)
        at com.mslv.oms.handler.order.cache.AbstractOrderCacheManager.getOrderByHistoryId(Unknown Source)
        at com.mslv.oms.handler.order.h.a(Unknown Source)
        at com.mslv.oms.handler.getorder.GetOrderHandlerEJB.process(Unknown Source)
        at com.mslv.oms.handler.a.processRequest(Unknown Source)
        at com.mslv.oms.jsp.processor.RequestProcessorSupport.a(Unknown Source)
        at com.mslv.oms.jsp.processor.RequestProcessorSupport.processRequest(Unknown Source)
        at com.mslv.oms.jsp.processor.RequestProcessorSupport.processRequest(Unknown Source)
        at com.mslv.oms.jsp.processor.RequestProcessorSupport.a(Unknown Source)
        at com.mslv.oms.jsp.processor.RequestProcessorSupport.a(Unknown Source)
        at com.mslv.oms.jsp.processor.OrderEditorProcessor.a(Unknown Source)
        at com.mslv.oms.jsp.processor.OrderEditorProcessor.a(Unknown Source)
        at com.mslv.oms.jsp.processor.OrderEditorProcessor.b(Unknown Source)
        at com.mslv.oms.jsp.processor.OrderEditorProcessor.processRequest(Unknown Source)
        at com.mslv.oms.jsp.controller.RequestController.a(Unknown Source)
        at com.mslv.oms.jsp.controller.RequestController.a(Unknown Source)
        at com.mslv.oms.jsp.controller.RequestController.processRequest(Unknown Source)
        at com.mslv.oms.jsp.controller.MainServlet.a(Unknown Source)
        at com.mslv.oms.jsp.controller.MainServlet.doProcess(Unknown Source)

 


Scenario 2:
=========
1. The current date is 2013-03-27” which is the same as the order creation date.
2. Submit a Current Dated Order [2013-03-27T16:00:00] with a revisionnumber of 1
3. Execute processing the order at accepted state in Task A1 4. Again submit first Revision with a  future dated
order[[2013-03-30T16:00:00]] and a revisionnumber of 2
5. Update the order in Task A1, it will move to “Ameding” order state and “Undo” execution mode.
6. Update the order it will not be visible in the task client but is visible in the osmwebui and calculate the future date requested delivery date and waiting for next start date.
7. Again submit second Revision with Current dated order[[2013-03-27T16:00:00]] and a revisionnumber of 3
8. Order will moves to amending state in “osmwebui” and wil throw errors.

<Error> <EJB> <BEA-010026> <Exception occurred during commit of transaction Name=[EJB com.mslv.oms.a
mendorder.AmendOrderMDB.onMessage(javax.jms.Message)],Xid=BEA1-1AAF0BA84BFF6BBCE573(1388595832),Status=Rolled back. [Reason=weblog
ic.transaction.nonxa.NonXAException: ORA-02091: transaction rolled back
ORA-02292: integrity constraint (ORDERMGMT2.FK_OM_ORDER_INST_04) violated - child record found
],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=29,XAServerResourceInfo[WLStore_OSM7221Domain__WLS_
AdminServer]=(ServerResourceInfo[WLStore_OSM7221Domain__WLS_AdminServer]=(state=rolledback,assigned=AdminServer),xar=WLStore_OSM72
21Domain__WLS_AdminServer1178506169,re-Registered = false),NonXAServerResourceInfo[WL_JDBC_LLR_POOL.oms_pool]=(ServerResourceInfo[
WL_JDBC_LLR_POOL.oms_pool]=(state=rolledback,assigned=AdminServer),nonXAResource=JDBC LLR, pool=oms_pool, table=ORDERMGMT2.WL_LLR_
ADMINSERVER),SCInfo[OSM7221Domain+AdminServer]=(state=rolledback),properties=({weblogic.transaction.nonXAResource=WL_JDBC_LLR_POOL
.oms_pool, weblogic.jdbc.remote.oms_pool=t3://[fe80:0:0:0:31b7:62b:3843:281b]:9001, weblogic.transaction.name=[EJB com.mslv.oms.am
endorder.AmendOrderMDB.onMessage(javax.jms.Message)], weblogic.jdbc.llr=oms_pool}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=AdminServer+[fe80:0:0:0:31b7:62b:3843:281b]:9001+OSM7221Domain+t3+, XAResources={WSATGatewayRM_Admin
Server_OSM7221Domain, WLStore_OSM7221Domain__WLS_AdminServer},NonXAResources={})],CoordinatorURL=AdminServer+[fe80:0:0:0:31b7:62b:
3843:281b]:9001+OSM7221Domain+t3+): weblogic.transaction.RollbackException: ORA-02091: transaction rolled back
ORA-02292: integrity constraint (ORDERMGMT2.FK_OM_ORDER_INST_04) violated - child record found

        at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1884)
        at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:376)
        at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:267)
        at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:617)
        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.jms.client.JMSSession.access$000(JMSSession.java:115)
        at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5170)
        at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
Caused by: weblogic.transaction.nonxa.NonXAException: ORA-02091: transaction rolled back
ORA-02292: integrity constraint (ORDERMGMT2.FK_OM_ORDER_INST_04) violated - child record found


Scenario 3:
===========
 (The difference between in scenario 2 and scenario 3 is that order was in the accepted state of TaskA and waiting at TaskA but in scenario 3 TaskA completed and order is waiting at Task B1)
1. Submit Current Dated Order [2013-03-27T16:00:00] with a revisionnumber of 1
2. Execute processing the order and complete the TaskA1 and with the order waiting at Task B1 in ProcessB.
3. Again submit first Revision with Future date order[[2013-03-30T16:00:00]] and revisionnumber is 2.
4. Order will change to “Amending” state immediately and move to TaskA1 “Undo” execution mode in ProcessA.
5. After Updating the order it will not be visible to the task client but is visible in the osmwebui as “In progress” order state and calculate the future date requested delivery date and waiting for next start date.
6. Again submit Second Revision with current date order[[2013-03-27T16:00:00]] and revisionnumber is 3.
7. Order will moves to amending state in “osmwebui” and throwing errors in log

 

<Error> <EJB> <sourav-PC> <AdminServer> <ExecuteThread: '13' for queue: 'oms.automation'> <oms-internal> <> <11d1def534ea1be0:-551a02b4:13dab155923:-8000-0000000000000f14> <1364377523077> <BEA-010026> <Exception occurred during commit of transaction Name=[EJB com.mslv.oms.amendorder.AmendOrderMDB.onMessage(javax.jms.Message)],Xid=BEA1-0E200BA84BFF6BBCE573(1855071877),Status=Rolled back. [Reason=weblogic.transaction.nonxa.NonXAException: ORA-02091: transaction rolled back
ORA-02292: integrity constraint (ORDERMGMT2.FK_OM_ORDER_INST_04) violated - child record found
],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=1,seconds left=29,XAServerResourceInfo[WLStore_OSM7221Domain__WLS_AdminServer]=(ServerResourceInfo[WLStore_OSM7221Domain__WLS_AdminServer]=(state=rolledback,assigned=AdminServer),xar=WLStore_OSM7221Domain__WLS_AdminServer1178506169,re-Registered = false),NonXAServerResourceInfo[WL_JDBC_LLR_POOL.oms_pool]=(ServerResourceInfo[WL_JDBC_LLR_POOL.oms_pool]=(state=rolledback,assigned=AdminServer),nonXAResource=JDBC LLR, pool=oms_pool, table=ORDERMGMT2.WL_LLR_ADMINSERVER),SCInfo[OSM7221Domain+AdminServer]=(state=rolledback),properties=({weblogic.transaction.nonXAResource=WL_JDBC_LLR_POOL.oms_pool, weblogic.jdbc.remote.oms_pool=t3://[fe80:0:0:0:31b7:62b:3843:281b]:9001, weblogic.transaction.name=[EJB com.mslv.oms.amendorder.AmendOrderMDB.onMessage(javax.jms.Message)], weblogic.jdbc.llr=oms_pool}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=AdminServer+[fe80:0:0:0:31b7:62b:3843:281b]:9001+OSM7221Domain+t3+, XAResources={WSATGatewayRM_AdminServer_OSM7221Domain, WLStore_OSM7221Domain__WLS_AdminServer},NonXAResources={})],CoordinatorURL=AdminServer+[fe80:0:0:0:31b7:62b:3843:281b]:9001+OSM7221Domain+t3+): weblogic.transaction.RollbackException: ORA-02091: transaction rolled back
ORA-02292: integrity constraint (ORDERMGMT2.FK_OM_ORDER_INST_04) violated - child record found

    at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1884)
    at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:376)
    at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:267)
    at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:617)
    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.jms.client.JMSSession.access$000(JMSSession.java:115)
    at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5170)
    at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
Caused by: weblogic.transaction.nonxa.NonXAException: ORA-02091: transaction rolled back
ORA-02292: integrity constraint (ORDERMGMT2.FK_OM_ORDER_INST_04) violated - child record found

    at weblogic.jdbc.wrapper.JTSLoggableResourceImpl.commit(JTSLoggableResourceImpl.java:371)
    at weblogic.transaction.internal.NonXAServerResourceInfo.commit(NonXAServerResourceInfo.java:331)
    at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:2303)
    at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:307)


Scenario 4:
==========
1. Submit Current Dated Order [2013-03-27T16:00:00] with a revisionnumber of 1
2. Again submit first Revision with Future date order[[2013-03-30T16:00:00]] with a revisionnumber of 2
3. Again submit Second Revision with Future date order[[2013-03-27T16:00:00]] with a revisionnumber of 3
4. Order will move to amending state in the “osmwebui” is not visible to the task client and is throwing errors in log.

<Error> <oms> <sourav-PC> <AdminServer> <ExecuteThread: '12' for queue: 'oms.automation'> <oms-internal> <BEA1-2A950BA84BFF6BBCE573> <11d1def534ea1be0:-551a02b4:13dab155923:-8000-0000000000002e51> <1364383102681> <BEA-000000> <amendorder.AmendOrderMDB: Failed to process amendment for order ID [415] amendment order ID [417]
java.lang.RuntimeException: Exception caught during visit of values for group node[root] due to null
    at com.mslv.oms.handler.order.cache.jboss.JBossOrderCacheManager.a(Unknown Source)
    at com.mslv.oms.handler.order.cache.jboss.JBossOrderCacheManager.a(Unknown Source)
    at com.mslv.oms.handler.order.cache.jboss.JBossOrderCacheManager.a(Unknown Source)
    at com.mslv.oms.handler.order.cache.jboss.JBossOrderCacheManager.a(Unknown Source)
    at com.mslv.oms.handler.order.cache.jboss.JBossOrderCacheManager.a(Unknown Source)
    at com.mslv.oms.handler.order.cache.jboss.JBossOrderCacheManager.a(Unknown Source)
    at com.mslv.oms.handler.order.cache.jboss.JBossOrderCacheManager.getLastSubmittedDocument(Unknown Source)
    at com.mslv.oms.handler.order.h.a(Unknown Source)
    at com.mslv.oms.amendorder.a.a(Unknown Source)
    at com.mslv.oms.amendorder.AmendOrderMDB.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.jms.client.JMSSession.access$000(JMSSession.java:115)
    at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5170)
    at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
Caused By: java.lang.NullPointerException
    at com.mslv.oms.handler.order.cache.jboss.JBossOrderCacheManager.a(Unknown Source)
    at com.mslv.oms.handler.order.cache.jboss.JBossOrderCacheManager.a(Unknown Source)
    at com.mslv.oms.handler.order.cache.jboss.JBossOrderCacheManager.a(Unknown Source)
    at com.mslv.oms.handler.order.cache.jboss.JBossOrderCacheManager.a(Unknown Source)
    at com.mslv.oms.handler.order.cache.jboss.JBossOrderCacheManager.a(Unknown Source)

 

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