My Oracle Support Banner

Failed To Connect And Send Request To SARM - SRT issue (Doc ID 1553447.1)

Last updated on MAY 11, 2022

Applies to:

Oracle Communications ASAP - Version 7.2.0 and later
Information in this document applies to any platform.

Symptoms

Tried to run sample using one of the POTS. Initially ran following:

$ java client.SRTJMSClient t3://<IP_ADDRESS>:<PORT> "System.asa1.ApplicationType.ServiceActivation.Application.1-0;7-2;ASAP.Comp.SRT.MessageQueue" "System.<ENV_ID>.ApplicationType.ServiceActivation.Application.1-0;7-2;ASAP.Comp.SRT.ResponseQueue" "/apps/ASAP72/SRT/sample/incomingXML/POTS-1.xml" myMessage weblogic webl0gic
Initial Context created...
Queue session created...
$

 

The EventQueueListener was throwing below error.

 

$ java client.EventQueueListener t3://<IP_ADDRESS>:<PORT> "System.<ENV_ID>.ApplicationType.ServiceActivation.Application.1-0;7-2;ASAP.Comp.SRT.ResponseQueue"

Queue name is System.<ENV_ID>.ApplicationType.ServiceActivation.Application.1-0;7-2;ASAP.Comp.SRT.ResponseQueue
To end program, enter Q or q, then
*************************
JMS Destination: <ENV_ID>.asap_jms_module!SRT.ResponseQueue
JMS DeliveryMode: 2
JMS Correlation ID:
JMS Priority: 4
Application Properties
----------------------
OSS_EVENT_TYPE: sa:createOrderByValueException
JMS_BEA_DeliveryFailureReason: 2
OSS_API_CLIENT_ID:
OSS_ORDER_TYPE:
OSS_APPLICATION_DN: System/<ENV_ID>/ApplicationType/ServiceActivation/Application/1-0;7-2;ASAP/Comp/
messageType: MyMsg
OSS_ORDER_PRIMARY_KEY:
JMSXDeliveryCount: 1
*************************
Received Text Message:
  
  Failed to connect and send request to SARM
  
*************************

 

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.