Problem with soap receiver adapter

[Former Member]

Hi All

I have Idoc sender and soap receiver in my scenario.

I am calling web service deployed on WAS.

The web service is getting called but the acknowledgement message in xi contains following system error acknowledgement because of which xi changes the status of message to WAIT and starts retrying.

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

- <!-- Inbound Message

-->

- <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.MessagingException: java.net.SocketTimeoutException: Read timed out: com.sap.aii.af.ra.ms.api.RecoverableException: java.net.SocketTimeoutException: Read timed out</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack />

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

</SAP:Error>

Please anybody can help to resolve this problem. This scenario has worked without any error previously.

Thanks in advance

Beena

[bhavesh_kantilal · Accepted solution]

Hi,

Is this an Asynch Call? If yes, turn of Idoc acknowldegements by adding the entries in the table IDXNOALE.

if no, can you give more details on the scenario?

Regards,

Bhavesh

[Former Member · Accepted solution]

Hi Bhavesh,

It is an Async call where method does not return anything.

I added entries in IDX_NOALE but still it is setting the message status to WAIT and does retry.

Following is the Audit Log in Runtime workbench :

Audit Log for Message: 22b3052d-c519-034e-85db-e65d541d6414

Time Stamp Status Description

2006-12-13 10:25:23 Error SOAP: error occured: java.net.SocketTimeoutException: Read timed out

2006-12-13 10:25:23 Error Exception caught by adapter framework: Read timed out

2006-12-13 10:25:24 Error Delivery of the message to the application using connection AFW failed, due to: Read timed out.

2006-12-13 10:25:24 Success The asynchronous message was successfully scheduled to be delivered at Wed Dec 13 10:30:24 GMT+05:30 2006.

2006-12-13 10:25:24 Success The message status set to WAIT.

2006-12-13 10:30:25 Success Retrying to deliver message to the application. Retry: 1

2006-12-13 10:30:25 Success The message was successfully retrieved from the receive queue.

2006-12-13 10:30:25 Success The message status set to DLNG.

2006-12-13 10:30:25 Success Delivering to channel: INSPWCCT_PVtoSAP_Ack

2006-12-13 10:30:25 Success SOAP: request message entering the adapter

2006-12-13 10:35:28 Success SOAP: call failed

2006-12-13 10:35:28 Success SOAP: sending a delivery error ack ...

2006-12-13 10:35:28 Success SOAP: sent a delivery error ack

2006-12-13 10:35:28 Error SOAP: error occured: java.net.SocketTimeoutException: Read timed out

2006-12-13 10:35:28 Error Exception caught by adapter framework: Read timed out

2006-12-13 10:35:28 Error Delivery of the message to the application using connection AFW failed, due to: Read timed out.

2006-12-13 10:35:28 Success The asynchronous message was successfully scheduled to be delivered at Wed Dec 13 10:40:28 GMT+05:30 2006.

2006-12-13 10:35:28 Success The message status set to WAIT.

I have tried this scenario earlier. I am sending the same Idoc from R3 which was processed successfully earlier.

Thanks

Beena.

[bhavesh_kantilal · Accepted solution]

Beena,

java.net.SocketTimeoutException --> This normally indicates a network firewall / connectivity issue. Looks like there is some problem in the network connectivity between the XI server and your Webservice.

XI will by default try to restart the message 3 times at intervals of 5 minutes before the status of the message is changed from Waiting to System Error and that is why you are facing the Waiting message .

Just check from your network admin if the netwrok connectivity between the XI server and the webservice has been closed.If there is a proxy server, then you would need to add the proxy server setting in the Receiver SOAP adapter with the credentials.

Regards,

Bhavesh

[Former Member]

Hello,

Thanks for your help but turning off acknoledgement didnt help. The problem got resolved by configuring module parameter XMBWS.Timeout to increase default timeout of 5 minutes. Due to this it waits for more time before retrying to allow web service to finish execution.XI was waiting for web service to finish its processing.

Regards

Beena

[bhavesh_kantilal]

Beena,

thanks for the update!

><i>

The problem got resolved by configuring module parameter XMBWS.Timeout to increase default timeout of 5 minutes</i>

Can you also update where you made this change? Thanks,

Regards,

Bhavesh

[Former Member]

Hello Bhavesh,

I did this change in Integration Directory in module tab of communication channel.

I provided module parameter there.

Thanks

Beena

[bhavesh_kantilal]

Beena,

Which Module did you use? the standard module? I ahve never come across this parameter and hence the question?

Any documentation to which you can point me to?

Thanks a ton,

Regards,

Bhavesh

[Former Member]

Hello Bhavesh,

I used standard module.

You can refer to SAP Note 856597 which is about FAQs on SOAP adapter.

The parameter is mentioned in this note.

Regards

Beena