RFC Timeout error - com.sap.aii.af.ra.ms.api.MessageExpiredException:

[Former Member]

We have implemented an interface scenario XYZ (SOAP) <-> SAP XI <-> SAP ECC (RFC). The interface has been live for over a year now. Recently, some of the RFC calls are failing with the message u2018com.sap.aii.af.ra.ms.api.MessageExpiredException: Message dcdc644a-5d36-9d6b-e100-00008a539268(INBOUND) expiredu2019. We get this error after 3 minutes of waiting for RFC response. The RFC is taking more than 3 mins to execute (between 4 & 5 mins) as of the current data in the tables.

From the [Note 730870 - FAQ XI 3.0/ PI 7.0/ PI 7.1/ PI 7.11/ PI 7.2 RFC Adapter|https://service.sap.com/sap/support/notes/730870] u2013 Q 14, we realize that it may have been caused by RFC timeout parameter. But it was set to u2018300000u2019 msec when the error happened. We changed it to u2018600000u2019 and saw the same error i.e. timeout after 3 min. The RFC timeout param u2018syncMessageDeliveryTimeoutMsecu2019 made no difference.

We also looked at the Blog [XI: Timeouts, timeouts, timeouts....|https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/3802] [original link is broken] [original link is broken] [original link is broken]; and made sure that the PROCTIMEOUT is set to 600. IE Config HTTP_TIMEOUT is set to '10000'.

We fail to understand why we are getting this error in spite of setting the timeout parameters to recommended values. Are there any other timeout parameter that we need to look at?

We highly appreciate your inputs.

thx

praveen

[Former Member · Accepted solution]

Hope this discussion helps

Regards,

Manjusha.

[Former Member · Accepted solution]

thanks Manjusha, yes setting the parameter 'xiadapter.inbound.timeout.default' solved the issue.

[Shabarish_Nair]

got a chance to read thru this - https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c059d583-a551-2c10-e095-eb5d95e03747&overrid...