cancel
Showing results for 
Search instead for 
Did you mean: 

How to delete message in "Delivering" status. Only exists in Adapter Engine

Former Member
0 Kudos

Hi !

We have a strange problem. We have a message in "delivering" status, that appears to be blocking other threads of the same communication channel. That message, searching via MSGID in SXMB_MONI, does NOT exists.

There is only ONE entry in RWB, in the Adapter Engine. When trying to delete it from the RWB, it says "Unable to cancel", we are also unable to resend it from RWB.

How can we delete it ? is there any other administration tool or option?

Thanks !

Regards,

Matias.

Edited by: Matias Denker on Sep 17, 2008 5:01 PM

Accepted Solutions (1)

Accepted Solutions (1)

former_member183906
Active Contributor
0 Kudos

1.in VA, restart the service

server->services->SAP XI AF Messaging

2.

You can see the queues status (and number of stuck entries etc) through the link:

http://<host>:<port>/MessagingSystem/monitor/systemStatus.jsp

There, you can maintain the queues.

There is also a link for the EOIO Sequence Monitor:

http://<host>:<port>/MessagingSystem/monitor/sequenceMonitor.jsp

There you can see the stuck messages and maintain these.

Make sure to handle the proper message IDs.

All of these are acessible through the Messaging System main page:

http://<host>:<port>/MessagingSystem/

3. Check other document:

Archive and Delete Messages in SAP XI: A Step-by-Step Guide

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/402fae48-0601-0010-3088-85c46a23...

Answers (4)

Answers (4)

kenny_scott
Contributor
0 Kudos

Hi Matias,

to prevent one C.C. blocking other channels then see the notes :

[#1136790 Blocking receiver channel may affect the whole adapter type|http://service.sap.com/sap/support/notes/1136790]

[#1136474 XI 3.0/7.0: Setting Timeout for acquiring DB/FTP resources|http://service.sap.com/sap/support/notes/1136474]

To ensure that there are adequate consumer threads available then check if all the available File Receiver consumer threads are being used when messages stay in the u2018Deliveringu2019 or 'To Be Delivered' states

e.g.,

RWB -> Component Monitoring u2013 AE u2013 Engine status -> Additional Data

OR

http://<host>:<port>/MessagingSystem/monitor/systemStatus.jsp

OR

http://<host>:<port>/mdt/Systatus

If yes then increase adapter queue consumer thread allocation - refer to the SDN blog

Regards

Kenny

bhavesh_kantilal
Active Contributor
0 Kudos

Excellent Answer Kenny.

One of the biggest pain points for which I never knew the best solution. Now I know thanks to you!

Next time I get this issue ( and knowing my XI Development Box, I am sure I will definitely get this ) will try the list of steps you have provided above!

Regards

Bhavesh

pradeep_nellore
Participant
0 Kudos

Hi,

Restart of J2ee and J2se components would work.

If that does not work install patch 16 of sp20.

Thanks

--Pradeep

bhavesh_kantilal
Active Contributor
0 Kudos

You cannot delete a message in Delivering state.

To resolve this issue, if it is persistent, restart the AF Messaging Service in the Visual Admin and then this message should be delivered to the IE,

Regards

Bhavesh

Former Member
0 Kudos

Hi Bhavesh !

Thank you for your answer. We are going to try this. The message is is inbound (XI->FTP Adapter), so if you are right, after restarting the AF Messaging Service, the message should be delivered?

Thanks.

Regards,

Matias.

bhavesh_kantilal
Active Contributor
0 Kudos

It always works for me.. But, do not restart the AF Messaging service on a Production.. It bring the AE down for a few seconds!

Not sure if there is a better way to solve this issue though..

Regards

Bhavesh

bhavesh_kantilal
Active Contributor
0 Kudos

Hey Matias,

Did you find a better way to do this? Do let me know.

Regards

Bhavesh

Former Member
0 Kudos

Hi Matias

You are not able to cancel a message which in delivering status. I think we need to have monitoring (J2EE) role and/or PI Support role to perform this action. Please verify the user access.

Thanks

Sai