Error: call to messaging system failed

[Former Member]

Hi all,

i'm facing this error in a RFC type Communication Channel for every message.

"Error in processing caused by: com.sap.aii.af.mp.module.ModuleException: call to messaging system failed: com.sap.aii.af.ra.ms.api.MessageExpiredException: No response available. caused by: com.sap.aii.af.ra.ms.api.MessageExpiredException: No response available."

Entering the message i got that log:

"Audit Log for Message: 7e223c81-7c6c-11e0-a692-000c292557a5

Time Stamp Status Description

2011-05-12 09:50:23 Success RFC adapter received sRFC for ZXI_GROUNDWORK_START from SM7/100. Attempting to send message synchronously

2011-05-12 09:50:23 Success MP: Entering module processor

2011-05-12 09:50:23 Success MP: Processing local module localejbs/RfcAFBean

2011-05-12 09:50:23 Success Application attempting to send an XI message synchronously using connection RFC_http://sap.com/xi/XI/System.

2011-05-12 09:50:23 Success Trying to put the message into the call queue.

2011-05-12 09:50:23 Success Message successfully put into the queue.

2011-05-12 09:50:23 Success The message was successfully retrieved from the call queue.

2011-05-12 09:50:23 Success The message status set to DLNG.

2011-05-12 09:55:23 Error Transmitting the message using connection http://sxsixi118:8000/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.MessageExpiredException: No response available..

2011-05-12 09:55:23 Error The message status set to FAIL."

Can someone help me i've already verified it's not a timeout problem cause i've increased the timeout to 15 minutes without success.

Thanks in advance.

Daniele

[markangelo_dihiansan]

Hello,

Can you confirm if:

1. The receiving system is up?

2. The communication channel setting in ID is correct?

3. There is communication between PI and the receiving system?

4. The function module in R/3 is working correctly?

Please get back to us.

Hope this helps,

Mark

[Former Member]

Hello,

This certainly is some sort of timeout situation ! Response is taking too long to arrive, so XI/PI stops waiting and raises this error ! Which timeout parameter have you increased ? There are some params to influence this behaviour :

- RFC adapter's syncMessageDeliveryTimeoutMsec

- some XI adapter's xiadapter.inbound.* and xiadapter.outbound.* settings (check blogs for these entries), some are related to async and others to sync, can't remember exactly

Optimizing runtime processing is also a good idea

Rgds

Chris

[Former Member]

Already tried to increase to 900000 msec (15 minutes) but without result

[maciej_jarecki]

Hi ilrosso

Can you try to call other RFC using other RFC CC ? it will show us does RFC Adapter work ok.

Please also check on ECC side ST22 tcode for some error and ensure that RFC function return something and is in RFC mode

BR

Maciej

[Former Member]

The others rfc type communication channels work fine, sorry i didn't mentioned it before

[Former Member]

Which one did you increase ? Have you traced activity in your backend system ? Increasing timeouts may not be the best solution (you can't extend it to an infinite duration, that wouldn't make sense) so optimization or re-design (split load) could be necessary

Rgds

Chris

[maciej_jarecki]

Hi

So please check your RFC function. Run in manualy using SE37 with data that you pass from PI. Did you check St22 for errors ?

Regards

Maciej

[Former Member]

The data to the XI sistem are sent by Groundwork a IT montoring system

[Former Member]

i've icremented the parameter you described syncMessageDeliveryTimeoutMsec without results

[Former Member]

I think there is another one that needs to be in "sync" with this setting ! Now your RFC adapter can wait up to 15 minutes, but the XI core engine may still be limitied to 5 mins (300000ms) ... Try setting xiadapter.inbound.timeout.default to 900000ms !

Chris

Edited by: Christophe PFERTZEL on May 12, 2011 11:55 AM

[Former Member]

Now the erro that occurs is:

"Error in processing caused by: com.sap.aii.af.mp.module.ModuleException: call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Timeout caused by: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Timeout"

[Former Member]

It think it now means XI is able to get the timeout raised in SAP, and before, XI was closing the channel before getting it ? Are you able to explain why it takes so long ? Is this some queue picking bottleneck ? waiting ? SQL ?

Chris

[Former Member]

No because i didn't create the scenario and i've to resolve the problem

The log of the message is

"Audit Log for Message: 8e36e2b0-7ca3-11e0-9945-000c292557a5

Time Stamp Status Description

2011-05-12 16:24:32 Success RFC adapter received sRFC for ZXI_GROUNDWORK_START from SM7/100. Attempting to send message synchronously

2011-05-12 16:24:32 Success MP: Entering module processor

2011-05-12 16:24:32 Success MP: Processing local module localejbs/RfcAFBean

2011-05-12 16:24:32 Success Application attempting to send an XI message synchronously using connection RFC_http://sap.com/xi/XI/System.

2011-05-12 16:24:32 Success Trying to put the message into the call queue.

2011-05-12 16:24:32 Success Message successfully put into the queue.

2011-05-12 16:24:32 Success The message was successfully retrieved from the call queue.

2011-05-12 16:24:32 Success The message status set to DLNG.

2011-05-12 16:34:34 Error Returning synchronous error notification to calling application: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Timeout.

2011-05-12 16:34:34 Error Transmitting the message using connection http://sxsixi118:8000/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Timeout."

[Former Member]

Still not resolved. Any other idea?

[maciej_jarecki]

HI

Do you use some additional java module for this CC ? if not restart RFC service in NWA

BR

MAciej

[Former Member]

Already tried to restart but the errors remains the same