My Oracle Support Banner

Orders Stop Processing With Error - Please check that your keys are immutable, and that you have used synchronization properly. (Doc ID 1501347.1)

Last updated on OCTOBER 11, 2019

Applies to:

Oracle Communications Order and Service Management - Version 7.0.1 to 7.0.3 [Release 7.0.0]
Information in this document applies to any platform.

Symptoms

Orders stop processing with error -

####<Oct 20, 2012 1:06:38 AM CEST> <Notice> <Stdout> <hostname> <wls_server> <[ACTIVE] ExecuteThread: '6' for queue: 'weblogic.kernel.
Default (self-tuning)'> <> <> <> <1350687998536> <BEA-000000> <<20-Oct-2012 1:06:38,535 CEST AM> <ERROR> <ws.p> <[ACTIVE ] ExecuteThread: '6' for queue: 'weblogic.kernel.Default (self-tuning)'> <Error processing failOrder>
com.mslv.oms.OMSException: Entry.next=null, data[removeIndex]=1912572=order type=CentralOrderManagementOrder [CentralOrderManagement Order (id=10001)]/order source=CentralOrderManagementOrder [CentralOrderManagementOrder (id=10001)] previous=1912572=order type=CentralOrderManagementOrder [CentralOrderManagementOrder (id=10001)]/order source=CentralOrderManagementOrder [CentralOrderManagementOrder (id=10001)] key=1956502 value=order type=CentralOrderManagementOrder [CentralOrderManagementOrder (id=10001)]/order source=CentralOrderManagementOrder [CentralOrderManagementOrder (id=10001)] size=10000 maxSize=10000 Please check that your keys are immutable, and that you have used synchronization properly. If so, then please report this to commons-dev@jakarta.apache.org as a bug.
      at com.mslv.oms.jsp.processor.RequestProcessorSupport.processRequest(Unknown Source)
      at com.mslv.oms.jsp.processor.RequestProcessorSupport.processRequest(Unknown Source)
      at com.mslv.oms.handler.cluster.HandlerAgent.run(Unknown Source)
      at com.tangosol.coherence.component.util.daemon.queueProcessor.service.InvocationService.onInvocationRequest(InvocationService.CDB:10)
      at com.tangosol.coherence.component.util.daemon.queueProcessor.service.InvocationService$InvocationRequest.run(InvocationService.CDB:1)
      at com.tangosol.coherence.component.util.DaemonPool$WrapperTask.run(DaemonPool.CDB:24)
      at com.tangosol.coherence.component.util.DaemonPool$Daemon.onNotify(DaemonPool.CDB:49)
      at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:35)


Changes

When there are high order processing loads in OSM Cluster, problem may happen.

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
Changes
Cause
Solution
References


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