PI RWB-Messages stuck in Delivering Status

Hi Experts,
PI 7.1
Scenario: Proxy to Mail (Outbound)
QOs: Exactly Once in Order
We are facing problem while sending messages to receiver.
Messages are stuck in Delivering status and the messages followed by them are going into holding status.
Messages in Delivering status has no audit logs.
Issue has started couple of months back. We took restart initially to rectify the barrier but it is happening again. This is repetitive issue and we are looking for permanent fix. Restart is not preferred resolution as it is a production system. Please suggest how can we overcome it? It would be a great help.

Hi Hardik
I've blogged about this issue recently. Please check out the blog:-
http://scn.sap.com/community/pi-and-soa-middleware/blog/2014/03/27/handling-and-preventing-messages-stuck-in-to-be-delivered-status
Rgds
Eng Swee

Similar Messages

Messages stuck in delivering status

Hi all,
I have an idoc-xi-ftp scenario with EO quality of service. For the very first tests we set up a file CC using nfs and everything worked fine.
Today I received the info to connect to the FTP server and introduce it on the file CC. The issue comes because some kind of problem writing on the ftp server leaves the messages in status "delivering" (DLNG). While FTP guys try to fix the issue (they don't know where he tissue is right now) I have switch again to NFS with the old configuration in order to allow the users to keep testing.
But the issue comes because now the messages being sent to NFS scenario are marked as to be delivered and they are not processed.
I'm suspicious about the delivering ones and I'd like to cancel, but the cancel button doesn't allow me to do it so I'm hanged in a circle.
Any ideas?
Thanks in advance,
David R.

Hi,
Yes, ABAP +Java implies a complete restart of the PI server, which is not recommended in the production environment.
Generally, this case is like a deadlock situation. We will not be able to either resend/cancel the messages in delivering.
So , best option would be to identify which server node these messages are stuck and then restart that server node.
With the server node restart these messages in Delivering are again reprocessed by the server.
Regards,
Younus

Receiver JDBC channel is stuck in "delivering" status.

Hi experts,
I have a IDoc -> JDBC scenario, and when the JDBC channel tries to process a message, it get stuck in "delivering" status. Here's the log of the message process:
2011-04-25 17:38:10 Success Message successfully received by messaging system. Profile: XI URL: http://xq0ds001:50100/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
2011-04-25 17:38:10 Success Using connection JDBC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2011-04-25 17:38:10 Success Message successfully put into the queue.
2011-04-25 17:38:10 Success The message was successfully retrieved from the receive queue.
2011-04-25 17:38:10 Success The message status set to DLNG.
2011-04-25 17:39:08 Success Delivering to channel: CC_JDBC_NA_Familiares_BUXIS_Receiver
2011-04-25 17:39:08 Success MP: Entering module processor
2011-04-25 17:39:08 Success MP: Processing local module localejbs/CallSapAdapter
2011-04-25 17:39:08 Success Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
2011-04-25 17:39:09 Success JDBC adapter receiver channel CC_JDBC_NA_Familiares_BUXIS_Receiver: processing started; party , service BS_NA_BUXIS_QA
Any ideas of what could be causing this?
Many thanks!
Vanesa.-

Hi Vanesa,
Make sure you have set the MaxThreadCount parameter to 350 or higher depending of the case and of the resources available.
To increase the parameter, please follow the instructions below:
1. In the left frame choose Server -> Kernel -> ApplicationThreadManager
2. In the tab Display Configuration (right frame) choose Switch between view and edit mode to activate the edit mode.
3. The parameter MaxThreadCount must be set to 350.
4. You will then need to restart the J2ee
For reference see note #937159 - XI Adapter Engine is stuck
For specific setting to an adapter can be done by going to Services -> SAP XI AF Messaging
Look at the property 'Messaging connections' here you will see the following queues:
Send.maxConsumers (asynchronous sending - outbound)
Recv.maxConsumers (asynchronous receipt - inbound)
Call.maxConsumers (synchronous sending - outbound)
Rqst.maxConsumers (synchronous receipt - inbound)
Depending on where the bottleneck is occurring (i.e. too many entries in the Send.maxConsumers) you can increase these parameters.
Example of parameter value syntax (sample for JDBC adapter):
(name=JDBC_http://sap.com/xi/XI/System, Send.maxConsumers=15, Recv.maxConsumers=15, Call.maxConsumers=15, Rqst.maxConsumers=15)
For reference see note:
#791655 - Documentation of the XI Messaging System Service Properties
And see the link:
/people/kenny.scott/blog/2007/08/20/messaging-system-queue-properties-after-xi-30-sp19-xi-70sp11
Regards,
Caio Cagnani

Messages getting stuck in Delivering status in AE

Hi all,
Recently we are coming across messages that go into Delivering status. These messages mostly belong to File Sender/Receiver Adapter but not confined to them. Here is the audit log of one such message:
2011-03-21 10:01:55 Success Write to file "/usr/sap/ZX2/EXT/XI_INTERFACES/SCP2PIF016/NOT_PROCESSED/goodsReceiptPosting_InvalidRecords20110321-100155-650.xml" as binary, size 1949 bytes
2011-03-21 10:01:55 Success File processing complete
2011-03-21 10:01:55 Success MP: Leaving module processor
2011-03-21 10:01:55 Success The message was successfully delivered to the application using connection File_http://sap.com/xi/XI/System.
2011-03-21 10:01:55 Error Setting the message status to DLNG failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: Error updating status..
On searching in SDN I found one work around-- to restart Messaging Service in Visual Admin. This did work as the messages got processed after that. But, the problem seems to be recurring now(once in every two days).
Can any body shed some light on this to find the permanent fix?
Thanks a lot,
Gokul.

Hi,
Make sure you have set the MaxThreadCount parameter to 350 or higher depending of the case and of the resources available.
To increase the parameter, please follow the instructions below:
1. In the left frame choose Server -> Kernel -> ApplicationThreadManager
2. In the tab Display Configuration (right frame) choose Switch between view and edit mode to activate the edit mode.
3. The parameter MaxThreadCount must be set to 350.
4. You will then need to restart the J2ee
For reference see note #937159 - XI Adapter Engine is stuck
For specific setting to an adapter can be done by going to the Visual Administrator -> Services -> SAP XI AF Messaging
Look at the property 'Messaging connections' here you will see the following queues:
Send.maxConsumers (asynchronous sending - outbound)
Recv.maxConsumers (asynchronous receipt - inbound)
Call.maxConsumers (synchronous sending - outbound)
Rqst.maxConsumers (synchronous receipt - inbound)
Depending on where the bottleneck is occurring (i.e. too many entries in the Send.maxConsumers) you can increase these parameters.
Example of parameter value syntax (sample for FILE adapter):
(name=FILE_http://sap.com/xi/XI/System, Send.maxConsumers=10, Recv.maxConsumers=10, Call.maxConsumers=10, Rqst.maxConsumers=10)
For reference see note:
#791655 - Documentation of the XI Messaging System Service Properties
And see the link:
/people/kenny.scott/blog/2007/08/20/messaging-system-queue-properties-after-xi-30-sp19-xi-70sp11
Regards,
Caio Cagnani

Messages are stuck in "delivering" status

Hi
We are doing Async RFC to JDBC Scenario. Messages are successful from R/3 to XI but getting stuck at receiver jdbc adapter . subsequent message are also stuck because of this
Below is the audit log of the message
2007-06-29 10:33:08
Success
The message status set to DLNG.
2007-06-29 10:33:08
Success
Delivering to channel: CS_CUS_PS_MAINTENANCE
2007-06-29 10:33:08
Success
MP: entering
2007-06-29 10:33:08
Success
MP: processing local module localejbs/CallSapAdapter
2007-06-29 10:33:08
Success
Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
2007-06-29 10:33:08
Success
JDBC adapter receiver channel CS_CUS_PS_MAINTENANCE: processing started; party , service BUS_MES
After then it just hangs and it shows "delivering" status only
There is no error in SXMB_MONI
Any clues!!!!!!!!!!!!!!
Regards
Vijay

Vijay,
The queues in adapter are different from the queues in Integration Engine.
You can restart failed msg in adapter queues also. Stefan Grube has shown this in a weblog. Just do a search, you will get the blog.
Regards,
Jai Shankar

Messages stuck in Holding status in Runtimeworkbench

Hi,
Some Messages are stuck in Runtime workbench of PI in Holding status,When I resend the messages they return to same status again.
The messages are sent on 15-5-2014.I could not find those messages either in SXMB_MONI or SMQ2.
Now how to resend the messages successfully.Appreciate your help in this.

Hi Gurudatta,
If it is EOIO then you can go the Messaging System and there you can find the message which is blocking the other queues. Check the first message and delete it
And go to runtime work bech ---Message Monitoring --Adapter Engine and filter Holding message and Resend/cancel the first holding message
If it is not successfull stop and start the recevier communication channel. This will work
Regards,
SK

Message stuck in SXMB_MONI status " Sceduled for Outbound Process." Urgent

Hello All,
All messages in our XI environment are getting stuck with status Scheduled for Outbound Processing ...I have already done the following..
1) Registered the Queues
2) Deleted entries in SMQ1 and SMQ2 and restarted messages
Last time we had this issue, we were finally able to reslove it by doing a J2EE restart. But this has resurfaced again within a week, and this time even the restart is not working.
Do you think some parameter has been set incorrectly during the install ..
Any help would be appreciated ..
thanks
Mayank

Hey Mayank,
Did you got JCO failure error for any of XI message before start of getting this error message?
If so it's failing because of RFC connection problem...
You need to go to Tcode : SM59 in your xi server
check the TCP/IP Connections which is created while post-installation phase..
1. AI_RUNTIME_JCOSERVER.
2. AI_DIRECTORY_JCOSERVER
Solution : Increase the default value for CPIC_MAX_CONV (se note 314530).
Hope this wull solve your problem.
Nilesh

Adapter Engine Message in Delivering Status

Hi All,
Any idea how to cancel/delete the messages which are in delivering status in Adapter Engine.
In my case a single EOIO message is stuck in the AE with delivering status. Other messages are flowing successfully using the same cc.
Earlier during such cases we had to restart j2ee/ stop/start AF Messaging to resolve the problem.
Just wondering if theres any other solution?
btw : The message was in delivering status because the password mentioned in the receiver channel was wrong. There were other messages which failed but the status of those messages went into "System Error". Nothing wrong with that, but just wondering why did a single message remain in the "Delivering" status.
I have already been through this thread Re: How to delete message in "Delivering" status. Only exists in Adapter Engine and didnt find/understand anything which could help me.
Thanks
Sumit

Look at these blogs,
How to deal with stuck EOIO messages in the XI 3.0 Adapter Framework : How to deal with stuck EOIO messages in the XI 3.0 Adapter Framework
XI : How to Re-Process failed XI Messages Automatically
Message stuck in Adapter Engine queue with status "Delivering"
Hope this helps

Issue with PI messages in "To be Delivered" Status

Hello Experts,
We have a Mail to SOAP scenario on PO 7.4 single stack PI system. Currently we are facing issue with messages where messagess are in status "To be Delivered". Messages dont get processed further.
Two days back, we had issue with file system table overflow and this cause messages remained in "Delivering" status. I can see Audit log with error emssage for table space full.
I couldnt cancel/resend those messages.
I believed these messages are causing rest of the messages to go in "To be Delivered" status. I found few blogs to check resources in Java Engine Additional Data->Queues and its looks good.
we had system restart and these "Delivering" messages were cancelled but again when we tried a fresh run and first message went into "Delivering" Status with 500 server error message in audit log and subsequent messages started going into "To be Delivered" status. This is happening only for one scenario, rest of the message are working fine.
I tried wit new BS, Channel, Integrated scenario for same functioanlity but its not working.
Recent messages with "To be Delivered" can be seen with below audit log
Information MP: processing local module localejbs/sap.com/com.sap.aii.adapter.mail.app/XIMailAdapterBean
Information Mail: Calling the module processor for channel CC_Sender_V2
Information Mail: Message leaving the adapter (call)
Information Trying to put the message into the send queue
Information Application attempting to send an XI message asynchronously using connection AFW
Information Message successfully put into the queue
Information Trying to put the message into the send queue
Information Mail: Call completed
Information Message successfully put into the queue
Information The application sent the message asynchronously using connection AFW. Returning to application
Information Mail: Call returned for channel CC_Sender_V2
we have latest patch(SAP_XIESR Version 1000.1.70) applied 10 days back only
Kindly suggest.

Hi All,
Thanks for your reply and suggestions.
Now messages are flowing properly. Issue was with data population in the target structure. Receiver side we have Knowledge Management portal website and CreateDocument operation fields were expecting some values to be populated. We tried few combinations and it worked.
We also tried changing mapping and we could reproduce messages with "To be delivered" status.
Now we are searching for KM Portal Webservice documentation where information about every field of operation is mentioned. If we straight away pass source mailbody to webservice, its not working. failing at webservice end with error 500 internal server error. It expects data to be in Base64 format and also fields like Length of data to be populated. If we get documentation then things would be more easy. We are also passing attachment but its not getting generated at target end. We are not sure if webservice support that feature.
Thanks,
Vinit.

Delivering Status in Messaging system

Hi,
I am monitoring messages in messaging system. I can see some message status as "Delivering" from so many days. I am unable to delete those messages. It is not even changing to undelivered status. Please help.
Thanks,
Gunasree

Hi Gunasree,
The messages in the DELIVERING status can not be cancelled. The messages might have gone to delivering stage due to many reasons. If some earlier message got failed in the queue or the connection between the Receiver and adapter engine break...or some other reason.
For messages in the delivering status it can be cancelled by stopping the adapter engine only.
Thanks
Ajay

Messages stuck in TO BE DELIVERED status

Hi !
Suddenly, whenever a message has to use the File Adapter, no mather which communication channel is to be used, the message is stuck with the "TO BE DELIVERED" status.
These messages, all have SUCCESSFUL status in the SXMB_MONI. The problem is in adapter engine. ALL have NO errors in their Audit Log. Because the problem is in adapter engine/framework, obviously queues at SMQR/SMQ1/SMQ2 are emtpy. ALL have QoS = EO (no eoio queue is used, NO predecessor messages are stuck with system error).
This occurs no mather which adapter is the sender (RFC, File, etc.)
The audit log is:
2008-04-10 16:59:34
Success
Message successfully received by messaging system. Profile: XI URL: http://xxxxxxx:yyyyy/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
2008-04-10 16:59:34
Success
Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2008-04-10 16:59:34
Success
Message successfully put into the queue.
If we try to resend the message using the "resend" button in RWB, the message keeps in the TBDL state and the only difference is a new "success" entry in the audit log saying that:}
"Success | Admin action: Trying to redeliver message".
We already refreshed the cache and restarted the Java stack.
Any clues?
Thanks !
Regards,
Matias.

Hi,
Statuses such as HOLDING or FAILED usually happen only for delivery semantics EOIO (exactly once in order) or BE (best effort means Asynchronous). TO_BE_DELIVERED occurs while the message is put into the Messaging System receive queue. This is done via the Messaging System receive servlet:
http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>/<PROTOCOL>
The MS returns HTTP 200 to the Integration Server only if this was executed successfully. In this example scenario, status TO_BE_DELIVERED should not appear since we assume that the IS has called the servlet successfully.
The status is updated from TO_BE_DELIVERED to DELIVERING when the message has popped out of the receive queue and the event handler lookup was successful, so there is a small gap where TO_BE_DELIVERED could remain in the message monitor, although it was delivered from IS successfully.
Regards,
Srini

Stuck in To Be Delivered Status in Message Monitoring - Adapter Engine

Hi,
I have messages stuck in To Be Delivered status in Messages Monitoring. When i checked the Audito Logs, there are NO LOGS. I resent the message and now the logs indicated in the Audit Logs is:
2014-03-26 08:39:10
Information
The message was successfully received by the messaging system. Protocol: XI URL: http://<host>:<port>/MessagingSystem/receive/AFW/XI Credential (User): PIIXXXX
2014-03-26 08:39:10
Information
Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2014-03-26 08:39:10
Information
Message successfully put into the queue.
2014-03-26 08:52:48
Information
Admin action: Trying to redeliver message.
The connection between the receiver is ok, does this have something to do with the Communication Channels?
Please help.
thank you.

Hi Eng Swee,
there are messages that were cancelled yesterday and the status is 'Terminated With Errors'
this is what is indicated in the Audit Logs
2014-03-26 02:38:47
Information
Admin action: Trying to fail message.
2014-03-26 02:38:47
Error
The message status was set to FAIL.
2014-03-26 02:38:47
Information
Admin action: The message was successfully set to status failed.
2014-03-26 02:38:47
Error
Asynchronous error detected: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Message failed by admin.. Trying to report it.
2014-03-26 02:38:47
Error
Asynchronous error reported.
Is this the reason why the messages are stuck?
thank you!

Message stuck in Adapter Engine queue with status "Delivering"

Hi All,
I have a File to File EOIO scenario. The messages are sucessfully delivered from IE to AE. All entries have a chequered flag in SXMB_MONI. No messages are stuck in IE queue (SMQ2). But the message is stuck in AE queue with status "Delivering". I can not resend or cancel the message coz the status is "delivering".
The reason it is in "delivering" status is due to some config error that I made in Communication Channel FTP parameters. Now it is corrected. But how do I deal with this message now?
Restart of server is not an option here. Is there are place I can delete the message from AE queue?
Thanks
Jaishankar

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/
Regards,
Henrique.

Messages stucked "To be delivered" and "Delivering" Status.

Hi,
Lots of messages are stucked in Adapter engine with status "To be delivered" and "Delivering" in our production system.
We found out there is some FTP connection problem with one of the interface which runs only few messages per day. Because of the problem of this interface, it is stopping many other critical interfaces to process and all these messages are falling "To be delivered" and "Delivering" status. All these interfaces are running in File adapters but going to different servers.
If there is problem with one server(One file adapter), why is it stopping all the other interfaces to process?
What might be the problem and how to solve it?
PS: As a temporary solution we are solving this issue by restarting the java stack.
Thanks
Deepthi.

Hi,
Check the below SAP Note Q.47
https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=821267
Which talks about the maximum concurrency..which means that the threads can be controlled for a particular adapter..
As you said there are multiple ftp adapters and because of one its affecting all..
To avoid this the maximuum no of threads awarded to one adapter can be controlled so that the remaining threads can be used by other adapters...
For example...
Assume problematic adapter might be running for every 5 min...
Another adapters are running for every half an hour...
Before first run of another adapter , problematic adapter might have run for 5 times and occupies all 5 threads (thread wont get release as it will be in Delivering state...) remaining threads (another adapter threads) will go into ToBeDelivered state...
if you activate above parameters...only the assigned no of threads to particular adapter will be in Delivering (assume no as 2) then there will be 3 threads remaining which can be utilised by other adapters...
HTH
Rajesh

BPM wait step : RWB"To Be Delivered status": SXMB_MONI"Message being sent"

Hi All,
I have a BPM interface running fine since 1 year.
In this BPM I have wait step for 5 minutes.
But yesterday message is stopped on wait and not proceeding ahead.
I checked XML is good as per mapping. and in runtime wirk bench message is still in "To Be Delivered status"
and in SXMB_MONI message column Outbound Status still showing "Message being sent" even after 12 hours.(wait is only 5 minutes). And below is the trace of last message.
Please guide how to handle or restart this message. in SMQ1 & SMQ2 there are no queues showing:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface Request_SI</Trace>
<Trace level="1" type="T">select interface namespace https://www.XXXXX.com/YYYY</Trace>
<Trace level="1" type="T">--start determination of receiver interface action</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface Request_SI</Trace>
<Trace level="1" type="T">select interface namespace https://www.XXXXX.com/YYYY</Trace>
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
</SAP:Trace>
Regards

Solved, few BASIS jobs were inactive in transaction code "SWF_XI_CUSTOMIZING".

PI RWB-Messages stuck in Delivering Status

Similar Messages

Maybe you are looking for