cancel
Showing results for 
Search instead for 
Did you mean: 

Proxy to SOAP Adapter Scenario - Sometimes Message getting failed in XI RWB

Former Member
0 Kudos

Hi All

We are facing an issue in SAP XI messages. Please help if anyone faced similar kind of issue as explained below:

.We have a scenario in SAP-XI, where we are sending the PO data from SRM to third party .Proxy is being used at Sender side and SOAP Adapter is used for Receiver Communication Channel.

· Most of the cases the messages are being processed successfully and showing the XML payload as well in RWB. But sometimes it is being failed in XI RWB for u2018java.lang.NullPointerExceptionu2019. For these failed messages we are not able to see the XML payload as well in XI RWB while these messages are showing successful status in MONI in SRM and XI and we are able to see the payload as well in MONI.

· If we are resending the failed message from XI RWB, it is getting failed again with the same error. On the other hand if we are initiating the message again from SRM to Hubspan for the same PO, it is getting processed successfully in RWB but still not showing XML payload in RWB.

The erros which is being displayed in Audit log of RWB is as follows

Audit Log for Message: 4eb9a213-b6f3-09d7-e100-8002ac130c38

Time Stamp Status Description

09.11.2011 Message successfully received by messaging system. Profile: XI URL: http:/fac4sap01:573001MessagingSystemfreceive/AFW/X1

01:32:10.393 Success Credential (User): PlISUSER

09.11.2011

01:32:10.403 Success Using connection SOAP_http://sap.coinki/X1System. Trying to put the message into the receive queue.

09.11.2011

Success Message successfully put into the queue.

01:32:10434

09.11.2011

Success The message was successfully retrieved from the receive queue.

01:32:25024

0911.2011 'Display Nessaqe Details I

The message status set to DLNG.

Success

01:32:25.026

09.11.2011

01:32:25.028 Success Delivering to channel: CC_3PL_TNT_SND

0911.2011

Success MP: Entering module processor

01:32:25.028

09.11.2011

Success MP: Processing local module localejbsisap.comicom.sap.aii.af.soapadapterMISOAPAdapterBean

01:32:25.028

09.11.2011

Success SOAP: request message entering the adapter with user J2EE_GUEST

01:32:25.028

09.11.2011 SOAP: Target uri:

Success

01:32:25.029 http:/Nvebservices.cevalogistics.comadernaMiebServices/Ordertvlanagement/OrdermanagementWebService.asinx

09.11.2011 Error SOAP: call failed: javalang.NullPointerException

01:32:25.086

09.11.2011

Success SOAP: sending a delivery error ack

01:32:25.096

09.11.2011

01:32:25.096 Success SOAP: sent a delivery error ack

09.11.2011 Error MP: Exception caught with cause com.sap.aii.afra.ms.api.RecoverableException: java.lang.NullPointerException

01:32:25.097

09.11.2011 Error Exception caught by adapter framework: null

01:32:25.097

09.11.2011 Error SOAP: error occured: com.sap.aii.aftains.api.RecoverableException: javalang.NullPointerException

01:32:25.097

09.11.2011 Delivery of the message to the application using connection SOAP_http://sap.cointaXISystem failed, due to:

01:32:25.108 Error com.sap.aii.atrains.api.RecoverableException: javalang.NullPointerException.

09.11.2011

Success The message status set to WAIT.

Message part:

Message Display Tool (Detail Display)

Message Data Message Content Aucirt Log

Message Part: ISOAP Document u2022 u20221

SOAP Document

content-length: 16380 accept-encoding:gzip sap-xi-messageid:4E89A2F386F309D7E1008002AC130C38 http:POST host:ac4sap01:57300 user-agent:SAP Web Application Server (1.0;700) content-type:multipart/related;boundary=SAP_4E867782D3530320E1008000AC130C38_END:type="text/xmln;stE soapaction:nhttp://sap.com/xi/XI/Nessage/30"

<SOAP:Envelope xmlns:SOAP=1http://schemas.xmlsoap.org/soap/envelope/1><SOAP:Header><sap:Main xmlns:z

Please help me in solving the issue.

thank you

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

If it is showing successful in moni, it should be showing the same in RWB also. Check whether it is happening for other soap adapter scenarious also.

I strongly suspect it might be due to some issues with cache or connectivity with soap adapter itself. I believe it is not able to persist the message. Check with your basis guys on this.

Regards

Krish

Former Member
0 Kudos

Hi,

Can you check with third party if they receive anything when the error occurs on your side?

Can it be a temporary error on the receiver side?

Regards, Martin