SOAP sender channel MessageExpiredException: Message(INBOUND) expired

[former_member281534]

Hello All,

We are getting an error in a SOAP sender channel MessageExpiredException: Message(INBOUND) expired .

This error has started lately. There has not been any change/modification at parameter level.

Scenario of the interface is SOAP to CRM RFC synchronous channel.

Action taken so far :

   1.  Checked RFC TCP connection in CRM  system .

   2. Checked ST22 in CRM for any error logs.

   3 . Created a Dummy SOAP channel. The dummy channel was in error once message started to flow.

I have read all the related blogs but couldn't find a solution.

Any inputs will be appreciated ?

- Shreya

[vadimklimov · Accepted solution]

Hi Shreya,

MessageExpiredException is normally raised if response message wasn't delivered to a sender PI/PO application (which is commonly sender adapter application) within configured time in synchronous communication. To be more precise, when the sender application in PI/PO creates an XI message (which is commonly outcome of sender adapter flow execution), corresponding thread is then suspended and waits for either response message or MessageExpiredException (even for synchronous interfacing, processing in Messaging System is still asynchronous - that's why original thread is suspended and control is passed to another thread).

Having this in mind, there are various reasons why MessageExpiredException can be raised - few of commonly faced are:

• Workload / system performance issue in a PI system and/or a receiver system which prevented timely processing of request and/or response message - for example, lack of parallelism or other resources shortage;
• Long running logic in PI - for example, long running mapping execution or receiver channel execution. If large messages are processed, this can also be related to database processing. Additional pipeline processing steps like virus scanning or XML validation can also contribute to this delay;
• Long running logic in a receiver system;
  
• Network issues between PI and a receiver system;
• Too small value of a corresponding timeout (if it was adjusted globally in XPI Adapter: XI service or set in a sender communication channel).
  

Generally speaking, any delay in processing followed by sender application execution in PI, can cause MessageExpiredException in synchronous interfacing.

Regards,

Vadim

[former_member281534 · Accepted solution]

Hello Vadim,

Thank You for the inputs.

We have checked the possibilities mentioned by you.

. We have started facing this issue since 1 week and still the issue persists. The message load has been the same for this interface throughout . However, we can't completely rule out PI system performance issue.

But my query is why would the problem start suddenly .

. As per execution of mapping  and XML validation, we have encountered Read Timeout issue for this interface caused in mapping transformation step.

. There are no network issue currently with PI and Receiver system(SAP CRM)

[former_member186851 · Accepted solution]

Hello,

Any change happened in structure of RFC or mapping changes?

[vadimklimov · Accepted solution]

Hi Shreya,

It may not be a permanent problem (for example, some sporadic peak or performance degradation), so I would suggest checking audit log of the message that failed with MessageExpiredException, and identify steps where it spent most of its time. Based on this, we can narrow down possible areas that could contribute to message processing delay.

If there were several messages that failed with this exception, please check their audit logs and see if there is any common pattern of processing time distribution and delays for all of them.

Another way of identifying steps which consumed majority of processing time (especially if you have many messages being passed through that interface and looking into them one by one is not an option), is to look into Performance Monitor in PIMON, this will provide you with aggregated statistics regarding time consumed by which processing step.

Regards,

Vadim

[former_member281534]

Hello All,

Thanks for the inputs.

The issue has been resolved now.

There were error messages getting stuck in QRFC and TRFC. Also, huge number of work processess in READY state, so messages were not able to process resulting into MessageExpireException.

After clearing the entries, messages were processed.

Regards

Shreya

[nitindeshpande]

Hello Shreya,

Clearing the queues is just an temporary solution. I would request you to go through my blog mentioned below and implement the steps provided to resolve the queues issue permanently -

http://scn.sap.com/community/pi-and-soa-middleware/blog/2015/07/13/queues-issues-in-sap-pi-and-ecc-s...

Regards,

Nitin

[marksmyth]

Hi Shreya,

Check the wiki below for known tuning points which improve the flow in synchronous scenarios such as you have described above.

PI Troubleshooting Tips: How to Tune PI Synchronous Scenarios

Regards
Mark

[former_member182412]

Hi Sheyaswi,

Check this document for more about synchronous timeouts in PI

Regards,

Praveen.

[former_member186851]

Hello Shreyaswi,

Did you run the program in SE37 and check whether the RFC is working fine.

[former_member281534]

Hello Raghuraman,

The RFC at the CRM end is working fine .