OrderDataUpdate Has Failed In Amending Resulted From Updating Non-existent Node On JBoss Cache (Doc ID 1527374.1)

Last updated on JULY 10, 2017

Applies to:

Oracle Communications Order and Service Management - Version 7.0.3 and later
Information in this document applies to any platform.

Symptoms

On : 7.0.3 Patch 17 of OSM, Order Request Processor

ACTUAL BEHAVIOR
---------------
OrderDataUpdate has failed in Amending resulting in updating a non-existent node in the  JBoss cache . User received an OrderUpdateException in amending error.

In this test scenario, the order was amended twice. The first amendment succeeded, but following one failed.

The error message indicates that OrderDataUpdate operation had tried to update non-existent nodes. However,  it was confirmed that the order node can be found by the GetOrder and GetOrderHistory APIs. OSM might failed to load all or some of node items in the JBoss Cache.

Tried the test scenario on the server with more memory(14GB), where we got the same exception.

We created orders 3 times, the first one is a new order, the 2nd and the 3rd  ones are both amending orders for the first order. After the 3rd order was  created, we received an error at an automation task. 
OSM seemed to have failed to update the order nodes because it could not find  them. 
   
  ####<2012/11/17 13¿24¿07¿ JST> <Error> <oms> <apsrv01> <AdminServerOSM9> 
  <ExecuteThread: '12' for queue: 'oms.automation'> <oms-automation> 
  <BEA1-2BB3146E1C70D342E930> <> <1353126247368> <BEA-000000>   <designCircuitNoManage.designCircuitNoManageResponce: [ order ID=586 hist.   ID=88198 task mnemonic=designCircuitNoManage] Unable to update order data   for task [order ID=586, order history ID=88198, task   mnemonic=designCircuitNoManage] with XML [<OrderDataUpdate 
  xmlns="http://www.metasolv.com/OMS/OrderDataUpdate" 
 com.mslv.oms.handler.order.cache.jboss.NodeNotFoundException: Attempt to   retrieve non-existent node from cache   parentFqn[/586/root/0/kaisenKousuHansu/1937/sekkei/1938] nodeId[1309573]   nodeIndex[1353122365558]

 

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