Intermittent issue in PI-com.sap.aii.af.ra.ms.api.MessageExpiredException

[Former Member]

Hi everbody,

We are with Intermittent problem in SAP PI 7.0.

Some messages have this error below:

<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.MessageExpiredException:

Message 4bdefeac-f3e8-01de-e100-8000ac103265(INBOUND)

expired</SAP:AdditionalText>

##########################

The error above is appearing in Synchronous messages in trx sxi_monitor.

We read the note 730870 and the timeout parameters is ok.

We tried to stop/start in 'SAP XI AF CPA Cache' and 'SAP XI AF Messaging' but it not worked.

We have one message in a SAP but I think they do not have idea yet.

The adapters are involved are RFC and SOAP.

We changed the parameters:

- 'xiadapter.inbound.timeout.default' from 180000 to 300000 .

- 'syncMessageDeliveryTimeoutMsec' from 300000 to 600000 .

- 'syncMessageRemover.checkInterval' from 60 to 5 .

Please, could you have some idea to resolve this issue ?

ps: The error started after the stop/start for renew certification in keystore (j2ee) .

Best Regards,

Victor Yamanaka

[Former Member · Accepted solution]

Hi victor,

could you please refer the Note 791379

Extract from a FAQ :

At the beginning of a synchronous RFC call the RfcAdapter (sender channel) builds up the XI request-message and will send this to the Adapter Engine with a timeout. After this it will wait till the response-message reaches or the timeout expires. In case of timeout the exception named above is thrown. The timeout used by RfcAdapter for synchronous calls can be configured for the whole RfcAdapter as a property of the RfcAdapter J2EE Service. To change it's value open the service properties sheet like and change the value of "syncMessageDeliveryTimeoutMsec". Notice that this value is specified in milliseconds. After changing the property store the properties by clicking the save-button (disk symbol) on top of the page.If a similar error messages is shown for a receiver channel the timeout setting is done in the inbound XI-Adapter of the Adapter Engine and not via the above described setting in the RFC-Adapter. The value of xiadapter.inbound.timeout.default from J2EE Service 'SAP XI Adapter: XI' is used in this case.

similar forum post :

see if you have not referred this already.

Regards,

Srinivas

[Former Member · Accepted solution]

Hi Srinivas,

Thanks a lot. I read the information but I found one error that it occurs after 3 min after between the messages

below:

2010-05-04 10:08:15 Success The message status set to DLNG.

2010-05-04 10:11:16 Error Received XI System Error. ErrorCode: GENERAL

ErrorText: com.sap.aii.af.ra.ms.api.MessageExpiredException: Message

19d9e390-577e-11df-bab0-562430004002(INBOUND) expired ErrorStack:

I am thinking the error is not in our time-out parameters but in something

that it influences in our system to increase the time to the process.

Best Regards,

Victor Yamanaka

[Former Member · Accepted solution]

Hello Everybody,

I really appreciate all support.

The problem was resolved with "Cache Refresh Full" !

http://<hostname>:<port>/CPACache/refresh?mode=full

About the timeout parameters, I changed to the old value and the system work very well.

Regards and Thanks a lot!

Victor Yamanaka