cancel
Showing results for 
Search instead for 
Did you mean: 

Messages stuck in AE with To be delivered status

Former Member
0 Kudos

Hi Experts,

We are facing an issue with messages in AE having to be delivered status. The audit log in RWB shows status as below:

"The message was successfully received by the messaging system. Protocol: XI URL: http://xxxx:50000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER

Using connection JDBC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.

Message successfully put into the queue"

We checked the Thread count which is also not utilizing maximum threads.

We tried full cache refresh but of no use.

Please help to solve this problem.

Thanks

Manaswitha.

Accepted Solutions (0)

Answers (3)

Answers (3)

aashish_sinha
Active Contributor
0 Kudos

HI,

Filter on old messages for ERROR/System Error/Waiting and cancel all of them.

Then reprocess all "To Be Delivered" messages.

Regards

Aashish SInha

Former Member
0 Kudos

Hi Manaswitha,

Since the messages belongs to EOIO, check the message failures for past dates...until u clear the previuos messsages you cannot solve this problem.

Former Member
0 Kudos

Hi Manaswitha,

Good Day!

Could you please check whether these are EOIO messages and make sure no failure for this interface.

If the previous messages failed or errored, unless you cancel it. Remaining messages will not pass through.

Before cancelling any messages which are in system error. Please note down the message ID and take screenshot of all the data.

Send email to client for cancellation of system error message. Then refresh it.

This will help us to resolve this issue.

Have a nice day!

Regards,

Hari Suseelan

Former Member
0 Kudos

Hi Hari,

The messages are EOIO only but no message got failed.All the messages are in TO Be Delivered status.

Former Member
0 Kudos

Hello Manaswitha,

if they are EOIO you can look for the sequence (=queue) ID of them and then perform a search with that ID as a parameter. This should hopefully bring you the first message in the sequence. Something must be wrong with that first message. And it may have been sent some time ago.

Regards,

Jörg