ORDER_RELEASE_TIMEOUT_PARAM is not Being Picked up from OMS-CONFIG.XML in a Cluster (Doc ID 1453698.1)

Last updated on MARCH 29, 2023

Applies to:

Symptoms

There is a cluster timeout occurring when attempting to move an order from a managed server to a managed server in a cluster.
 
Managed server 2 is receiving an automation JMS message, then the Automation is trying to do a getOrder.  The lock on the order is trying to be moved from managed server 6 to managed server 2.  However this cannot be done due to a timeout exception.
 
This looks to be coherence problem from the stack trace  and an OSM Exception is raised.  The Exception does not indicate what is timing out.  So from the current data there is no way determine if a timeout parameter needs to be changed, or if there is some other problem.
 
It looks like the coherence exception is eaten and a OSM exception is raised in its place.
 
 
In managed server 2 the following exceptions is occurring:
 
  05:55:47,302 ERROR AutomationException:? - An automation exception has
  occurred At
  AutomationDispatcherImpl.runAutomator:/automation/plugin/internal/task/v21_th
  in/1.0/validate_configuration_a/do , the reason is
  :com.mslv.oms.automation.AutomationException:
  com.mslv.oms.automation.AutomationException: com.mslv.oms.OMSException:
  Failed to get handler for request due to Failed to acquire exclusive
  ownership of order(s)[2411026] from cluster member[managed6] due
  to Timeout while attempting to release order[2411026] from local
  server[managed6] after 30 seconds.
  com.mslv.oms.automation.AutomationException:
  com.mslv.oms.automation.AutomationException: com.mslv.oms.OMSException:
  Failed to get handler for request due to Failed to acquire exclusive
  ownership of order(s)[2411026] from cluster member[managed6] due
  to Timeout while attempting to release order[2411026] from local
  server[managed6] after 30 seconds.
  at com.mslv.oms.automation.plugin.AutomationEventHandlerImpl.a(Unknown
  Source)
  at
  com.mslv.oms.automation.plugin.AutomationEventHandlerImpl.processMessage(Unkn
  own Source)
  at com.mslv.oms.automation.AutomationDispatcher.onLocalMessage(Unknown
  Source)
  at com.mslv.oms.automation.plugin.AutomationEventHandlerImpl.a(Unknown
  Source)
  at com.mslv.oms.automation.plugin.d.a(Unknown Source)
  at
  oracle.communications.ordermanagement.cluster.message.ClusterMessageHandlerBe
  an.onMessage(Unknown Source)
  at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466)
  at
  weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.
  java:371)
  at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
  at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4585)
  at weblogic.jms.client.JMSSession.execute(JMSSession.java:4271)
  at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3747)
  at weblogic.jms.client.JMSSession.access$000(JMSSession.java:114)
  at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5096)
  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: com.mslv.oms.automation.AutomationException:
  com.mslv.oms.OMSException: Failed to get handler for request due to Failed
  to acquire exclusive ownership of order(s)[2411026] from cluster
  member[managed6] due to Timeout while attempting to release
  order[2411026] from local server[managed6] after 30 seconds.
  at com.mslv.oms.automation.OrderContextImpl.getOrder(Unknown Source)
  at com.mslv.oms.automation.plugin.AbstractAutomator._runAutomator(Unknown
  Source)
 
 
  and in Managed server 6 the following exception is occurring:
 
  05:45:18,011  INFO EMSRequestHandler:183 - Calling archiveEMSRequest method
  05:45:18,012  INFO EMSRequestHandler:260 - Enetering into archiveEMSRequest
  method
  05:45:18,013  INFO EMSRequestHandler:262 - Calling getArchivalLocation
  method
  05:45:18,013  INFO EMSRequestHandler:690 - Entering into getArchivalLocation
  method
  05:45:18,014  INFO PropertiesLookUp:137 - Start of
  PropertiesLookUp.getInstance()...
  05:45:18,011 ERROR c:? - Timeout while attempting to release order[2411026]
  from local server[managed6] after 30 seconds.
  com.mslv.oms.OMSException: Timeout while attempting to release
  order[2411026] from local server[managed6] after 30 seconds.
  at oracle.communications.ordermanagement.cluster.c.c(Unknown Source)
  at oracle.communications.ordermanagement.cluster.c.b(Unknown Source)
  at
  oracle.communications.ordermanagement.cluster.impl.AgentRequestBalancerImpl$3
  .run(Unknown Source)
  at
  com.tangosol.coherence.component.util.daemon.queueProcessor.service.Invocatio
  nService.onInvocationRequest(InvocationService)
  at
  com.tangosol.coherence.component.util.daemon.queueProcessor.service.Invocatio
  nService$InvocationRequest.run(InvocationService)
  at
  com.tangosol.coherence.component.util.DaemonPool$WrapperTask.run(DaemonPool)
  at
  com.tangosol.coherence.component.util.DaemonPool$Daemon.onNotify(DaemonPool)
  at com.tangosol.coherence.component.util.Daemon.run(Daemon)
  at java.Thread.run(Thread.java:619)
  05:45:18,020  INFO c:? - Processing request from remote server to release
  order[2411152] from local server[managed6]. If the order is
  present in cache it will be removed.
  05:45:18,030  INFO c:? - Processing request from remote server to release
  order[2411151] from local server[managed6]. If the order is
  present in cache it will be removed.
  05:45:18,031  INFO b:? - Removed order /2411151 from orchestration cache due
  to request from remote server to release this order.
  05:45:18,015  INFO PropertiesLookUp:92 - Config file has been updated and
  Data being Re-Cached
 

 

Changes

Cause

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