Delay of Message in the Adapter Engine when put into queue

[Former Member]

Hi XI/PI Experts,

We are having problems in the Adapter Engine wherein messages are staying longer in the AE queue as usual. Sometimes, it stays longer in Delivering status also. Is there any way we can monitor and try to push the message out of AE to avoid delays? I know we can do this in the ABAP side (Integration Engine)...but how can we do this in the Adapter Engine?

See below sample logs in AE RWB:

2008-07-17 13:28:13 Success Using connection SOAP*****. Trying to put the message into the receive queue.

2008-07-17 13:28:13 Success Message successfully put into the queue.

2008-07-17 13:34:12 Success The message was successfully retrieved from the receive queue.

2008-07-17 13:34:12 Success The message status set to DLNG.

As you can see there is a gap of 4 minutes.

Hope you can help me. Thank you so much in advance.

Grace

[Former Member]

Hi.

Thanks for your answers but the messages are not set into EOIO but just EO. So the messages are not ending up in Holding Status.

I also believe that issue is not occurring because of too many messages in error in AE nor because of the receiving system is down. Issue is happening when message is about to be sent to the SOAP communication channel in AE. As you can see in the sample log I provided above, in RWB AE, after the message was put into queue, it took several minutes to be delivered to corresponding comm channel. My questions are:

1. Is there a way we can monitor the queue in AE like the way we monitor the queue in IE? (e.g. smq1 and smq2 transactions) .

2. If there is a way, how are we going to intervene manually on the queues in AE? (we can intervene with smq1 and smq2 in IE)

3. For messages with Delivering Status in AE, sometimes it is taking hours to move to "Successful/Delivered" Status. Is there a way we can intervene with that? I believe we can resend messages with "System Error" Status and Staus "To be Delivered" but for status "Delivering"...it is not possible (from what I know -- I hope there is a way).

I look forward to hearing from you guys/gals.

Grace

[Former Member]

>>Is there any way we can monitor and try to push the message out of AE to avoid delays

No its not possible,even if you do this,the you will get half processed messages in Integration engine and will fail there.

>>I know we can do this in the ABAP side (Integration Engine)

I m not sure which process you do here,but if you are talking about setting the Timeout parameters,then even that doesn't push the message out,it fails(just as adapter engine fails after a certain time).

Only way to avoid this to fix the reason for this delay,but you can't push half processed messages without forcing them to fail.

Thanx

Aamir

Edited by: Aamir Suhail on Jul 17, 2008 11:06 AM

[Former Member]

Hi,

It is due to some Failed messages that reside in the AE.

Also many times delivery of messages fails for few interfaces and that stuck message create problem for other scenarios too.

Delete all the messages that are in System Error and.

Also check weather the target system is properly up or not. As XI will make few defaut trials if the receiver is down and in that duration if suddenly the receiver is up..Xi delivere the message...else put these messages in System Error status.

Thanks

Farooq.

[Former Member]

Hi,

This may help u

Regards

Seshagiri