Synchronous Call Timeout but the PO still created in ECC.

[Former Member]

Hi PI Expert,

I have problem with synchronous call (Web Service -

---

> RFC). Sometimes if the processing time in ECC take longer time the webservice will throw exception timeout but then the processing stil continue in receiver communication channel until success.

So if you use SXI_MONITOR you can see 2 transaction, Sender web service error timeout and RFC success.

<?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>XIServer</SAP:Category> 
  <SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code> 
  <SAP:P1>500</SAP:P1> 
  <SAP:P2>Timeout</SAP:P2> 
  <SAP:P3 /> 
  <SAP:P4 /> 
  <SAP:Stack>HTTP response contains status code 500 with the description Timeout Error while sending by HTTP (error code: 500, error text: Timeout)</SAP:Stack> 
  <SAP:Retry>N</SAP:Retry> 
  </SAP:Error>

But the RFC communication still able to continue until succes. Supposed to be both error if the sender communication channel timeout ?

  - <ns0:Z_MM_STO.Response xmlns:ns0="urn:sap-com:document:sap:rfc:functions">
  <EX_RESULT><RETURN><item><TYPE>E</TYPE><ROW>0</ROW><PARAMETER>POHEADER</PARAMETER><MESSAGE>0100905701</MESSAGE><MESSAGE_V1></MESSAGE_V1><MESSAGE_V2></MESSAGE_V2><SYSTEM></SYSTEM></item><item><TYPE>E</TYPE><ROW>1</ROW><PARAMETER>POHEADER</PARAMETER><MESSAGE>External document number 100905701 already assigned</MESSAGE><MESSAGE_V1>100905701</MESSAGE_V1><MESSAGE_V2></MESSAGE_V2><SYSTEM>ECPCLNT300</SYSTEM></item></RETURN></EX_RESULT> 
  </ns0:Z_MM_STO.Response>

Please advise is that anything that i can check ?

Thank You and Best Regards

Fernand.

Edited by: Fernad Lesmana on Aug 23, 2010 7:59 AM

Edited by: Fernad Lesmana on Aug 23, 2010 8:00 AM

Edited by: Fernad Lesmana on Aug 23, 2010 8:01 AM

[Former Member · Accepted solution]

Hi Sebastian,

is this configuration are you mention about ?

xiadapter.inbound.timeout.default = 180000 [ms] -

---

> messaging system wait response

icm/keep_alive_timeout (sec.) = 60 -

---

> sender webservice

How about "syncMessageDeliveryTimeoutMsec" in the RFC adapter ?

What is the different ?

I am using normal SOAP adapter for sender and RFC adapter for receiver.

Thank You and Best Regards

Fernand

[Former Member · Accepted solution]

Hi Fernand,

The last parameter (syncMessageDeliveryTimeoutMsec) you mentioned is for general timeout setting of RFC receiver calls (see note FAQ RFC Adapter: https://service.sap.com/sap/support/notes/730870). That one seems high enough in your case

xiadapter.inbound.timeout.default is the default setting of 180 seconds, which is normally the default for all timeouts in PI.

Normally in icm there's a setting for the http port (e.g. something like icm/server_port_x prot=http,port=500xx,timeout=180,proctimeout=180)

Can you confirm that one is higher then 60 seconds? (Just saw you saying something about 60 seconds before editing the posting)

Best wishes

Sebastian

Edited by: Sebastian Simon on Aug 26, 2010 1:24 AM

[Former Member]

Hi Fernand,

That looks like your HTTP timeout of the SOAP Sender is obviously lower then the one of the RFC connection.

If your transaction in the ECC takes longer then 60 seconds the Sender will be cut off from the connection, but the

RFC call still runs till the end (as far as i know it runs in a different thread in the adapter engine).

Do you use the regular SOAP Adapter and how does your scenario look exactly? It could be the HTTP timeout of your ICM or the SOAP Adapter itself. For the ICM the settings are made in the SMICM transaction.

For the Sender Adapter you can override it in the channel configuration as described in this note:

https://service.sap.com/sap/support/notes/856597

Best regards

Sebastian