Adapter Engine - File_http://sap.com/xi/XI/SystemRecv

[Former Member]

Hi all,

I have a problem on the PI Java side. Sometimes (once or twice in a month) messages get stuck in File_http://sap.com/xi/XI/SystemRecv. I see that it is 5/5 and new messages start to fill DispatchDisp queue.

When I look at message monitoring I see that 5 messages are in status delivering and the others are on Hold.

I don't know why this problem occurs. I searched the forum and saw some temporary solution. For example: "restart some services on the NWA side".

I want to know why this happens and solve this problem completely.

Thanks.

[Former Member]

Hi Aarman,

If problem persists even after increaing the no. of Queue threads in Messaging System service, DO not restart entaire Java engine. To fix this, just stop and restart the File adapter service present in NWA/Visual Administrator so that, this restart will not affect other adapter message processing.

Thanks,

RK

[marksmyth]

Hello

There can be different causes of this issue. The most likely being a lack of resources (queues/threads) available to the File_http://sap.com/xi/XI/SystemRecv connection, to process the volume of messages being sent to it.

As a first step ensure you have enough:

1) system level threads (see note #937159 XI Adapter Engine is stuck and ensure the MaxThreadCount parameter is set to 350 on all java nodes)

2) application level threads (see the blog /people/kenny.scott/blog/2007/08/20/messaging-system-queue-properties-after-xi-30-sp19-xi-70sp11). I'd recommend increasing the number of threads/queues available to the SystemRecv connection to 10.

It could possibly be a bug which is causing this. Check note #1604091 Messages delivered by File/JDBC receiver stuck in DLNG state, for one known issue.

Regards

Mark

[Former Member]

Thank you very much Mark and Shabarish!

We have high volume scenario running with file receiver. Hundreds of files are written in a very short time. So I will first check the threads.

I will check also the other cases and share with you the results.

Edited by: Arman Eker on Aug 24, 2011 11:53 AM

[rajasekhar_reddy14]

Hi ,

Refer below blog ,it explained cleary why this happens and with solution

/people/mike.sibler/blog/2011/01/26/tuning-the-pi-messaging-system-queues

We also having same problem with JDBC Adapter, i am working on different options(like incresing thred count and setting value MaxRecv value to appropriate value).

i will share excat solution for this soon.

Please let me know which version of PI are you working on.

Regards,

Raj

[Shabarish_Nair]

this could be an issue with the particular patch level you are on.

usually upgrading to the latest patches resolve these issues.

If the issue persist, i recommend you raise a message with SAP.

[Former Member]

Hi

Status - DLVG would imply that the messages were not be able to pushed to the target due to some problem at the Receiving Application side....These type of messages cant be cancelled or resent

HOLD - Messages - U can always identify the first message the put the queues onto HOLD state and then decide upon whether to cancel or resend the messages..

may be that might give u a fix...

Regards,

XA

[Former Member]

The problem is messages stay in delivering mode forever. I have to restart the Java side to clear this messages.

[Former Member]

Have you checked the SMQ2 queue?

[Former Member]

What has this to do with smq2?

Can you please give more details?