Time out - SOAP Receiver Channel

[Former Member]

Hi All,

My Scenario is Database --> PI (7.1) --> SOAP (synchronous) .

The WebService is taking around 15 mins for giving the Response back to PI SOAP Adapter.But, because of Time Out at the PI SOAP Receiver adapter , I am getting "INBOUND EXPIRED" error.

I referred the following links and tried to Increase the time out value in the SOAP Receiver communication channel - Module Parameters.But, this is not working.

1. Note : 856597

2.

Can you please let me know if there any possible approach to increase the time out for SOAP Receiver Channel ?

Thanks and regards,

Midhusha.

[former_member4985 · Accepted solution]

Hi,

Please try the cache refresh with the link:

"http://host:j2eeport/CPACache/refresh?mode=full"

Also, try:

- In Integration Repository/Directory go to menu Environment -> Clear SLD Data Cache

- In R/3 go to transaction SXI_CACHE -> menu XI Runtime Cache -> Start Complete Cache Refresh

Regards,

Caio Cagnani

[Former Member · Accepted solution]

Hi ,

I have checked the links and options mentioned above. Still, the same error ..Not able to increase the time out of SOAP receiver channel.

Thanks and Regards,

Midhusha

Edited by: Midhusha on Mar 10, 2011 7:35 AM

[aashish_sinha · Accepted solution]

Hi,

Lookout to below notes.

https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=791379

Note number - 791379

Regards

Aashish Sinha

[Former Member · Accepted solution]

Hi Aashish,

The mentioned note is referring to the parameters relating to the entire adapter engine which affects all adapters in common. I want to change only my SOAP Receiver adapter .

Thanks& Regards,

Midhusha

[aashish_sinha · Accepted solution]

Pleas look below note

https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=893713

note : 893713.

soap XMBWS.Timeout 120000

regards

Aashish Sinha

[naveen_chichili · Accepted solution]

Hi Midhusha,

even i had a experience in such a case recently and finally it was the problem at the webservice end.Please check from the other end also and also change the parameter as per the thread mentioned above and do the CPAcache refresh.

Thanks and Regards,

Naveen.

[Former Member · Accepted solution]

Hi Naveen,

Checked at the Webservice end , the webservice requires 10-12 mins time to have the cache built up and gives response back. I tried with " soap XMBWS.Timeout " in module parameters but this is not working.

Thanks & Regards,

Midhusha

[former_member186494 · Accepted solution]

I had met this issue recently, my scenario is used soap adapter to receive from thirdpart system and use rfc adapter to send to ERP system.

So we need to set parameter XMBWS.Timeout in soap adapter and "Timeout for Synchronous Communication in Milliseconds" of advance tab is rfc adapater.

I think these infomation is helpfull for someone.

[Former Member]

Your problem seems to be a case of connection timing OUT. I too encountered this error in one of my synchronous SOAP scenarios and later discivered the system on which Web service was running is not accessible.

Make sure all the ports are open and and you have connectivity to that system where the web service is running.

Hope this helps

Regards

Azahar

[aashish_sinha]

Hi,

Have a look to below discussions

Regards

Aashish Sinha