Error http

[Former Member]

Escenario:

HTTP Receiver

RFC Sender

this error appears in Response Msg ( trx sxmb_moni), every time is but recurrent, but we have not been able to find from where the error comes

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Call Adapter

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIAdapterFramework</SAP:Category>

<SAP:Code area="MESSAGE">GENERAL</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: No response available.</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack />

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Regards,

Ximena

[Former Member]

make the scenario async on RFC sender side and HTTP receiver side. Basically it should be both async or sync.

[Former Member]

The scenary es syn.

[Former Member]

to make myself clear..the intended process is...

an SAP system is making an RFC call to XI, which routes and makes and HTTP call and the HTTP response gets send back to the SAP system as RFC response...

is that correct ?

If that is the case...what is the response obtained in the program making the RFC call ? Also could you please post the way in which the RFC call is being triggered from SAP system to R/3 ?

Thanks.

[Former Member]

Inboun Message

<?xml version="1.0" encoding="UTF-8" ?>

- <ns0:Z_MM_ISSAPCOOR_DE018 xmlns:ns0="urn:sap-com:document:sap:rfc:functions">

<CHARG />

<LGORT>0001</LGORT>

<MATNR>000000000000102123</MATNR>

<WERKS>CT01</WERKS>

<WBS_ELEM>C070526NTT00STCK000</WBS_ELEM>

<STOCK_IND>Q</STOCK_IND>

- <TI_ZMMEIN018>

- <item>

<MATNR />

<WERKS />

<LGORT />

<CHARG />

<CLABS />

</item>

</TI_ZMMEIN018>

</ns0:Z_MM_ISSAPCOOR_DE018>

Request Message

<?xml version="1.0" encoding="UTF-8" ?>

- <ns0:Z_MM_ISSAPCOOR_DE018 xmlns:ns0="urn:sap-com:document:sap:rfc:functions">

<CHARG />

<LGORT>0001</LGORT>

<MATNR>000000000000102123</MATNR>

<STOCK_IND>Q</STOCK_IND>

<WBS_ELEM>C070526NTT00STCK000</WBS_ELEM>

<WERKS>CT01</WERKS>

</ns0:Z_MM_ISSAPCOOR_DE018>

Response ID

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Call Adapter

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIAdapterFramework</SAP:Category>

<SAP:Code area="MESSAGE">GENERAL</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: No response available.</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack />

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Mesage Interface : Consulta_Stock_OUT_SYN_MI

Outbuound mesage: Z_MM_ISSAPCOOR_DE018.Input

Input message: Z_MM_ISSAPCOOR_DE018.Output

[Former Member]

Could you also post the ABAP code which makes this RFC call ?

[Former Member]

I do not have access to R3 since it is an interface is in PRD

[Former Member]

still continuous the error

regards

XImena Gonzalez

[iprieto]

Hello Ximena,

Are you sure that target system send a reponse? Try to access to target system without input parameters, method GET and tell us the response.

Nex try to send a message into a web page to target system.

Good luck

Iván Prieto

[Former Member]

Hi Ximena,

Why dont u just goto SXMB_MONI and check the trace of the pipeline step in which u r geting the error.

Can u please post tht error....

Also check the adapter monitor...

Regards,

Akshay

Message was edited by:

Akshay Salunke

Akshay Salunke

[Former Member]

TRACE ERROR

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Call Adapter

-->

- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">

- <Trace level="1" type="B" name="CL_HTTP_PLAIN_INBOUND">

<Trace level="1" type="T">server-protocol HTTP/1.1</Trace>

<Trace level="1" type="T">content-type text/xml; charset=ISO-8859-1</Trace>

<Trace level="1" type="T">charset charset=ISO-8859-1</Trace>

<Trace level="1" type="T">user-agent Jakarta Commons-HttpClient/2.0.2</Trace>

<Trace level="1" type="T">host 10.233.50.55:8000</Trace>

<Trace level="1" type="T">content-length 8014</Trace>

<Trace level="1" type="T">remote-addr 192.168.180.85</Trace>

</Trace>

<Trace level="1" type="T">COMMIT is expected by application !</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />

- <!-- ************************************

-->

<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />

- <!-- ************************************

-->

<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />

<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />

<Trace level="1" type="T">****************************************************</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">XMB entry processing</Trace>

<Trace level="1" type="T">system-ID = XIP</Trace>

<Trace level="1" type="T">client = 300</Trace>

<Trace level="1" type="T">language = S</Trace>

<Trace level="1" type="T">user = XIAPPLUSER</Trace>

<Trace level="1" type="Timestamp">2007-02-07T13:55:45Z CHILE</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">* *</Trace>

<Trace level="1" type="T">****************************************************</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />

- <!-- ************************************

-->

<Trace level="1" type="T">Message-GUID = F3AA032BFD859C4A883DD310660D217A</Trace>

<Trace level="1" type="T">PLNAME = CENTRAL</Trace>

<Trace level="1" type="T">QOS = BE</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />

- <!-- ************************************

-->

<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />

<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />

- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">

<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>

<Trace level="1" type="T">Cache Content is up to date</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />

- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">

<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>

<Trace level="1" type="T">Cache Content is up to date</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />

- <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV">

<Trace level="1" type="T">number of receivers: 1</Trace>

<Trace level="1" type="T">Single-receiver split case</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />

- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">

<Trace level="1" type="T">Interface Mapping urn:vivesap:sap:legacy:coord Pedidos_Ventas_IM</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />

- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

<Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV" />

</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />

- <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">

<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP" />

</Trace>

</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />

- <!-- ************************************

-->

</SAP:Trace>

[Former Member]

Did you check the receiving programme? I had the same problem as the callback never came....

[Former Member]

to be more comprehensive, The ABAP programme that Calls RFC does not seem to finish the transaction. See if you can find any commit work expressions in it

[Former Member]

this program does not use the commando commit work

[Former Member]

in monitoring runtime workbench..

this error..

com.sap.aii.af.ra.ms.api.MessageExpiredException: Sync application request expired.. Setting message to status failed

[Former Member]

This error may occur when your sender is synch, but the receiver is asynch.

Can you check your scenario to see if this is the case? Also, check if the inbound and outbound interfaces are both synch.

Regards,

Bill