Msg Struck to be Delivered Status in RWB

[Former Member]

Hi All,

.

In Adapter Engine it is specifing the message is Delivered

Why messege get Struck with the Delivered Status in RWB

and it taking lot of time to deliver.

So Please any one help out for solution ASAP.

[former_member307485 · Accepted solution]

Hi Venkat,

Status: TO_BE_DELIVERED

Which means that the message was successfully delivered from Integration Server point of view and it states that the messages is initially handed over to the Messaging System.

TO_BE_DELIVERED occurs while the message is put into the Messaging System receive queue.

Solution:

This is done via the Messaging System receive servlet:

http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>;

/<PROTOCOL>

Only if this was executed successfully the Messaging System returns HTTP 200 to the Integration Server and the Status TO_BE_DELIVERED moves to DELIVERING

Try logging into Sap GUI with two users: XIAPPLUSER & XIAFUSER

to see if they are blocked

We can check the messages:

AdapterFramework

com.sap.aii.adapterframework.serviceuser.language

com.sap.aii.adapterframework.serviceuser.name = XIAFUSER

com.sap.aii.adapterframework.serviceuser.pwd

ApplicationSystem

com.sap.aii.applicationsystem.serviceuser.language

com.sap.aii.applicationsystem.serviceuser.name = XIAPPLUSER

com.sap.aii.applicationsystem.serviceuser.pwd

in the exchange profile to make sure the right passwords

Regards,

Divya

[former_member184619]

Hi Venkat,

Hi have also faced the same problem, I tried the approach of deleting/modifying the ID objects and recreating it. I tried other options as well but nothing worked for me.

Try clearing the cahces as well, Check the cache status in ID->Enviornment->Cache status overview.

Sachin

[former_member206760]

restart your J2ee engine

[former_member200962]

Hi Tarang,

Is restarting the J2EE engine a feasible option...becoz this error occurs for most of the time and almost every XI/PI developer might have experienced it atleast once.....if we start restarting the entire J2EE engine each and every time for the sake of processing a single message wont that affect the processing of other interfaces?

Regards,

Abhishek.

[former_member206760]

you can go for restart only once or twice...but if the issue keeps on recurring then i think an oss should be raised

[Former Member]

Hey Venkat,

You need not restart your J2ee engine every time....... all u need to do is goto Visual Admin --> AF (Adapter Framework) services and take a restart of this particular service....this will not take a J2ee restart.

In case you want to avoid taking restarts of these services than you can apply the latest patch......SP17 wud help..

Dhwani

[former_member200962]

Hi,

The message comes in the To_Be_Delivered state because it is stuck in the queue....if you see the corresponding queue you will see your message stuck into it...check the queue for all the stuck, messages even of other interfaces...if one message gets stuck in a queue then all the following messages get stuck in it and their status is set to To_Be_Delivered....once the first message is released from the queue then the following messages will also get released...thats why you get the message after some time.....the below thread has the solution for this problem (it is already COPIED for your ease):

You can also check for the registration status of your queue in SMQR, and try unlocking the locked queue in transcation SMQ1 / SMQ2.

Regards,

Abhishek.

[former_member206760]

can u pl tell what is the status of the stuck messgaes

"delivering" or "to be delivered"

[Former Member]

Hi shah,

Its both "delivering" or "to be delivered", but presently we need to check "to be delivered"

[Former Member]

Hi,

If the adapter engine status shows as delieverd, then it is delivered. How do you say that the message is struck in AE.

Check in IE whether the message has arrived, check the queues smq2 and smq3 whether it is stuck in IE queue.