Order Update Failed: Message Cache Update Failure (Doc ID 2559816.1)

Last updated on MARCH 29, 2023

Applies to:

Symptoms

Order update failed: message Cache update failure

This problem happens when SOM orders are in fallout error for a great deal of time and is retried, then the SOM orders complete its fulfillment flow but its COM order is still in the  in-progress state, the COM order can’t update the complete status from its SOM order or when BRM returns the response later to COM, in Weblogic logs following message error:

<An error occurred processing XML request: 232 Order update failed : message Cache update failure: Cannot update node fqn
Then in Weblogic console we can verify updates messages are stuck in oracle/communications/ordermanagement/WebServiceCreateProvisioningOrderResponseQueue Queue

In Weblogic console messages are stuck in oracle/communications/ordermanagement/WebServiceCreateProvisioningOrderResponseQueue Queue

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.