SAF Message Blocked Intermittently when one of remote destination is down (Doc ID 1630379.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle WebLogic Server - Version 10.3.5 to 12.1.2.0.0
Oracle WebLogic Server - Version 10.3.4 to 10.3.4
Information in this document applies to any platform.

Symptoms

When one of the Managed Server of remote Domain is brought down, then SAF Agents would intermittently block new message as well and wouldn't forward any of the messages to the remote domain.

SAF Agent would continuously report error messages that "Failed to forward message to the down server" as below

<Debug> <JMSSAF> <posbap01> <osbSvr11> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <5e4370afb5b5f5fb:-5a42cc89:143dd899805:-8000-000000000001379d> <1390996447088> <BEA-000000> <Forwarder failed to forward the message TextMessage[ID:<990954.1390994196241.0>, <?xml version="1.0" encoding="...] to oms_jms_module!<Remote_Queue> stopPipeline= false hasNonFailedDDMembers true isExactlyOnceDDForwarding true failureCount 0
weblogic.jms.common.JMSException: JMSException while creating destination.
at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherAdapter.java:61)
at weblogic.jms.client.JMSProducer.toFEProducer(JMSProducer.java:1293)
at weblogic.jms.client.JMSProducer.deliveryInternal(JMSProducer.java:796)
at weblogic.jms.client.JMSProducer.forwardInternal(JMSProducer.java:523)
at weblogic.jms.client.JMSProducer.forward(JMSProducer.java:1500)
at weblogic.jms.client.WLProducerImpl.forward(WLProducerImpl.java:620)
at weblogic.jms.extensions.JMSForwardHelper.ForwardInternal(JMSForwardHelper.java:219)
at weblogic.jms.extensions.JMSForwardHelper.ForwardFromMessage(JMSForwardHelper.java:168)
at weblogic.jms.forwarder.Forwarder$Subforwarder.forwardInternal(Forwarder.java:1093)
at weblogic.jms.forwarder.Forwarder$Subforwarder.forward(Forwarder.java:909)
at weblogic.jms.forwarder.Forwarder$Subforwarder.pushMessages(Forwarder.java:802)
at weblogic.messaging.util.DeliveryList.run(DeliveryList.java:263)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: weblogic.jms.common.JMSException: JMSException while creating destination.
at weblogic.jms.frontend.FEProducer.checkAndProcessStaleness(FEProducer.java:805)
at weblogic.jms.frontend.FEProducer.sendSingleDestination(FEProducer.java:1209)
at weblogic.jms.frontend.FEProducer.send(FEProducer.java:1437)
at weblogic.jms.frontend.FEProducer.invoke(FEProducer.java:1496)
at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:961)
at weblogic.messaging.dispatcher.DispatcherServerRef.invoke(DispatcherServerRef.java:276)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:141)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: weblogic.jms.common.JMSException: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.jms.backend.<Remote JMS Server>'. Resolved 'weblogic.jms.backend'; remaining name '<Remote JMS Server>'
at weblogic.jms.frontend.FEManager.refreshBackEndId(FEManager.java:617)
at weblogic.jms.frontend.FEConnection.createDestination(FEConnection.java:886)
at weblogic.jms.frontend.FEConnection.createDestination(FEConnection.java:875)
at weblogic.jms.frontend.FEProducer.checkAndProcessStaleness(FEProducer.java:800)
... 10 more
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'weblogic.jms.backend.<Remote JMS Server>'. Resolved 'weblogic.jms.backend'; remaining name '<Remote JMS Server>'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1148)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:258)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:220)

 

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