My Oracle Support Banner

ASAP JMS Response Fails To Reach Upstream System via SAF (Doc ID 1509011.1)

Last updated on AUGUST 31, 2020

Applies to:

Oracle Communications ASAP - Version 7.0.1 and later
Information in this document applies to any platform.
***Checked for relevance on 02-MAY-2014***
***Checked for relevance on 19-OCT-2015***

Symptoms


OSM 7.0.3 on Weblogic 10.3.3 on Redhat EL 5.6
ASAP 7.0.1 on Weblogic 9.2.3 on HPUX 11.31

OSM sends createOrderByValueRequest via SAF to ASAP
ASAP receives message and sends createOrderByValueResponse via SAF to OSM
OSM does not receive message (nothing logged) and ASAP logs a failure

In AdminServer.log, following errors were logged repeatedly:

####<Sep 14, 2012 10:34:53 AM PDT> <Info> <JMS> <HOST_NAME> <WLS_SERVER_NAME> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (sel
f-tuning)'> <> <> <> <1347644093873> <BEA-040506> <The JMS SAF forwa
rder has successfully connected to the remote destination "t3://HOST_NAME:PORT/asap.activationEventTopic".>
####<Sep 14, 2012 10:34:53 AM PDT> <Info> <JMS> <HOST_NAME> <WLS_SERVER_NAME> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (sel
f-tuning)'> <> <> <> <1347644093987> <BEA-040507> <The JMS SAF forwa
rder failed to connect to the remote destination "t3://HOST_NAME:PORT/asap.activationEventTopic", because of weblogic.jms.common.LostServerExceptio
n: [JMSClientExceptions:055169]Network connection to server was lost.
       at weblogic.jms.client.JMSProducer.checkClosed(JMSProducer.java:949)
       at weblogic.jms.client.JMSProducer.publicCheckClosed(JMSProducer.java:954)
       at weblogic.jms.client.ReconnectController.checkClosedReconnect(Reconnec
tController.java:673)
       at weblogic.jms.client.WLProducerImpl.checkClosedReconnectGetProducer(WL
ProducerImpl.java:53)
       at weblogic.jms.client.WLProducerImpl.checkClosedReconnectGetProducer(WL
ProducerImpl.java:56)
       at weblogic.jms.client.WLProducerImpl.setUnitOfOrder(WLProducerImpl.java
:499)
       at weblogic.jms.extensions.JMSForwardHelper$Preserve.restore(JMSForwardH
elper.java:372)
       at weblogic.jms.extensions.JMSForwardHelper.ForwardInternal(JMSForwardHe
lper.java:229)
       at weblogic.jms.extensions.JMSForwardHelper.ForwardFromMessage(JMSForwar
dHelper.java:168)
       at weblogic.jms.forwarder.Forwarder$Subforwarder.forwardInternal(Forward
er.java:1021)
       at weblogic.jms.forwarder.Forwarder$Subforwarder.forward(Forwarder.java:
858)
       at weblogic.jms.forwarder.Forwarder$Subforwarder.pushMessages(Forwarder.
java:761)
       at weblogic.messaging.util.DeliveryList.run(DeliveryList.java:256)
       at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkMan
agerImpl.java:518)
       at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
       at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Caused by: weblogic.jms.common.LostServerException: server connection in state S
TATE_NO_RETRY


It appears that the connection to OSM was successfully open and then instantly closed for some reason.

Changes

 

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


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