XI Messages Stuck in DLNG Status

[Former Member]

We have to occasionally deal with messages being stuck in DLNG status. The usual way of resolving the problem is to either restart Messaging System Service or restarting the J2EE node where the message is stuck. This cause a lot of messages to fail in the production environment.

Is there any way to deal with this problem without restarting Messagng System Service/J2ee node or affecting any other message in the process of solving the problem?

[manikandan_shanmugam3]

HI,

seems messaages are got stuck in Queue in Adapter Engine.it can be resolve if you clear the AE Queue.

1)calcle all the messages which are in failed or waiting status.

2Resend the delevering status messages which you need to resend the early messages first and without this you cant resend the latest one.

Regards,

Manikandan

[Eoin_Kierans]

You can check the following blog:

' Messaging System queue properties after XI 3.0 SP19 / XI 7.0SP11 '

/people/kenny.scott/blog/2007/08/20/messaging-system-queue-properties-after-xi-30-sp19-xi-70sp11

If there is a backlog in one specific adapter framework queue you can increase the number of threads for this queue.

[Former Member]

Maciej, I didn't see any options to restart a thread, but thanks for reminding us of MMC.

Eoin, We have observed this problem on JDBC, File and RNIF adapters. The thread dumps show shortage of threads. We are afraid of increasing the number of threads due to OOM errors and long GC runs. We are thinking of re-allocating threads from senders to receivers.

[maciej_jarecki]

Hi

You can set separate thread numer for each adapte. Set it in messaging.connectionDefinition parameter of XPI Service: AF Core.

Kind Regards

Maciej

[Former Member]

Would like to have a look at it:

/people/rajeshkumar.pasupula/blog/2010/12/11/no-more-hassles-with-dlng-status-of-message-from-pi-73

This also explains the reason why message stucks in DLNG status !

[maciej_jarecki]

HI

Which PI version do you use. I saw scenerio that message has been delivered to target system but in PI AE the status was dlng.

in this case you can change message status manually.

King Regards

Maciej

[Former Member]

We have had this problem a lot of times. The root cause is network connectivity problem.

We use XI 3.0. We know that this problem could be avoided in PI 7.3, but upgrading to 7.3 will take time.

Thread dumps show that the thread has opened an I/O stream. That's all I could understand from it. Shouldn't there be a time out to end stream. We had left the problem unresolved for few hours on one occasion and it was in DLNG until we restarted Messaging System Service.

[Former Member]

Does any one know how to kill/restart a java thread?

[maciej_jarecki]

Hi

You have SAP Management Console - Java Applet on http://hostname:5xx13 and this will be usefull in your case.

Kind Regards

Maciej

[Former Member]

Hello Roshini,

First find out the root cause behind the stuck messages

It might be because of

1. The target system might not be available

2. Check whether there are any EOIO messages failed in that Q

3. Check for N/W issues towards the target system

Regards,

Moorthy