Sometimes a syncronous interface scenario SOAP-XI->RFC cancels with error com.sap.aii.af.ra.ms.api.MessageExpiredException: Message d3825660-1d5d-11db-aeb9-00112540039c(INBOUND) expired.
Usually - as mentioned in some of message threads in this forum - this error means that the timeout parameters of RFC adapter or J2EE engine are incorrect. But this is not the case, the parameter setting are OK. Additionally the start and ending times in message monitor are equal (within same second), thus for me indicating that it cannot be a timeout problem. Or is there a bug in message monitor that is shows start and ending date the same within this type of error?
Additionally if I executed the RFC function module in backend SAP system with same parameters as in the XI's call, and there is was no response problem.
Is there any other logical cause for expiration?
The XI logs does not tell much more than just this message expiration.
Some funny remark is also, that with these error situations, the message monitor shows the response message first and after that the request message. It should be vice versa I think.
We have got 3 Java servers and I think these cancelled messages was executed with server instance 0.
This problem only happens occasionally ( ~1-10 errors per day ) out of thousands of other successfull RFC interface calls. The interface that causes the error is not always the same either. There are 100 other syncronous interfaces and at the same time there could only a few in processing simultanously.
Best regards,
Kim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.