Work Order XML Sent To JSRP When ASAP Is Down Returns Remote exception (Doc ID 580143.1)

Last updated on DECEMBER 21, 2016

Applies to:

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

Symptoms

Two different behaviors have been observed from JSRP when WO is sent while ASAP is down.

1. In solaris env: If ASAP is down and its Weblogic is UP then if any WO is sent to
JSRP[createOrderByValueRequest XML] then after some time we get a response XML on the Topic as:

<sa:createOrderByValueException
xmlns:co="http://java.sun.com/products/oss/xml/Common"
xmlns:mslv-sa="http://www.metasolv.com/oss/ServiceActivation/2003"
xmlns:sa="http://java.sun.com/products/oss/xml/ServiceActivation"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<sa:remoteException>
<co:message>Failed to connect and send request to SARM</co:message>
</sa:remoteException>
</sa:createOrderByValueException>



2.However in HP UX env:If ASAP is down and its Weblogic is UP then if any WO is sent to
JSRP[createOrderByValueRequest XML] then nothing returns at the topic and the message remains in
the Queue and when ASAP is brought UP then it consumes the message and create the WO.


.

Changes

 

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