To Be Delivered Status for messages

Hi All,
I've a File->PI-File scenario. If I check the status of messages under RWB->Message Monitoring->Adapter Engine, I find some mesages with status "Scheduled". The single status of the messages is "To be delivered". Manually I try to send a single message but in the Audit Log I find "Admin action: Trying to redeliver message."
The Queue "DispatchDisp" is fill with all the messages.
How can I send these messages?
Thanks in advance
2009-02-11 17:11:20 Information Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2009-02-11 17:11:20 Information Message successfully put into the queue.
2009-02-11 21:13:15 Information Admin action: Trying to redeliver message.
2009-02-11 21:14:29 Information Admin action: Trying to redeliver message.

Your file is stuck in a queue where failed files are waiting to get resolved. So you need to clear the queues first and then process your file.
Here is the way to clear the queues for Failed messages with System Errors.
RWB --> Adapter Engine --> show additional criteria --> Enter the QUEUE NAME in field "Conversation_ID" (for this you have to first know the queue name from details of the messages having ststaus "Holding" or "to be delivered".) --> Expand "Configure table columns" --> choose "Conversation ID" and "Sequential Number" --> display. --> sort the list by ascending order of "sequential number" --> cancel the message whose sequential number is latest and go on canceling in ascending order.
Hope it helps.
Br,
Madan Agrawal

Similar Messages

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!

To Be delivered status in Message monitoring

Hi,
There are some messages in TO BE DELIVERED status in Message monitoring while selecting integration server. I could neither cancel nor resend.
any input reg. this will be appreciated.
I didn't see any messages with TO BE delivered status in adapater engine.
I could able to clear What ever messages in system error status in adapter engine by filtering based on sequential id.
I have seen this thread & link also.
To Be Delivered
Re: "To be delivered" status in RWB -- Any solution?
http://help.sap.com/saphelp_nw04/helpdata/EN/49/e3fb40ef74f823e10000000a155106/content.htm
I could not see any entry in SMQ1, SMQ2, SM58 also
Thanks
Praba
Edited by: Prabaharan Rangasamy on Dec 8, 2009 1:02 PM
Edited by: Prabaharan Rangasamy on Dec 8, 2009 1:04 PM

Hi,
You cannot resend or cancell the messages which are in status "To Be Delivered". Check Receiver adapter File/Jdbc/ OFTP e.t.c. which is processing these messages.
Check with your Basis team to remove the lock of adapters if any. Or to process these messages you require soft restart of Java stack.
I had same kind of issue two days back with OFTP adapter messages and did soft restart of java stack with help of Basis team.
Hope it will helps you
Cheers
Veera

To Be Delivered Status for AS2 messages

Hi Experts,
We have an issue with the EDI messages that are sent out of XI through AS2 Adapter. The messages were going out successfully till yesterday. From yesterday onwards, we see the messages under To Be Delivered Status in the Message Monitoring of Adapter Engine messages in RWB.
We have restarted the J2EE engine and it doesn't help.
The Service is not EOIO and hence the question of QUEUEs doesn't arise.
Did anyone ever face such an issue? Please help.
Regards,
Ravi Kanth

"To be delivered " occurs while the message is put into the Messaging System receive queue. It means that the message was successfully delivered from Integration Server and it is passed on to the Messaging System.
- Make sure that XIAPPLUSER XIAFUSER are not blocked
- Otherwise try retyping the passwords for XIAPPLUSER & XIAFUSER in exchanegProfile
- Restarting would be always helpful
Regards,
Prateek

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".

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

Log version status for message in PI message monitoring

Hi All,
we send IDocs from ECC to PI and then external systems. It's working fine all the time But third party system did not recieve only one message out of many. This missing message showing in PI is like LOG version when I look at in monitoring.It was happend long back and its still showing as scheduled.
And also there were no pending messages in the queue.
any idea what happend for this message exactly ?
Thanks .

Hello
Check the notes below:
#1471001 PI monitor: Synchronous response is displayed as log version
#1256891 Logging errors in synchronous communication
These may help explain/fix the error.
Regards
Mark

Messages in devivering status for long

Hi All,
I am in with a problem.I have an File XI RFC async scenario.While posting data to the RFC the message are kept on delivering status for very long .
If for this interface more than 5 files are kept all the othere messages are in to be delivered status which enlongens the queue.
Only 5 messages are getting delivered at a time as the number of RFC threads in XI Box is 5.
Please help me in this .
I had a thought that from XI side it was only a fire and forget type of scenario but is it possible that while delivering it waits for successfull compleation of the target systems application program.
Mudit Mehra

No not all but only a single interface is running slow.
Can you also explain on how to increase the parallet processes?
Mudit

Messages are hanged in "Delivering" status

Hi everyone,
I have an IDoc -> PI -> File scenario. Everything works fine until the message reaches the file adapter. In the Communication Channel monitoring there is no activity for that message, and the channel is correctly configured and started. However, in the Message Monitoring, when I filter for my receiver interfacce, I see that there are 4 messages that have been in "Delivering" status for 2 days. Then, there are a lot more messages in "To Be Delivered" which I guess are waiting for the first ones to finish.
I stoped & started the channel, I tried to resend the messages and nothing happened. Any suggestions? Thank you very much!
Regards,
Pablo

Hi Pablo,
"However, in the Message Monitoring, when I filter for my receiver interfacce, "
--- First Remove all the filters in the RWB,
now set the status filter as "System Error" and select the date range for more than six months or 1 yr ...
now if you see any message then delete them,
Again set the status to "To Be Delivered" and delete all of them.
now set the status to "Delvering" and restart them,
this is what i do when ever i face this problem.
Regards,
Karna...

Applescript for Messages status

Hello,
I try change status for Message app
I use that script to set offline status:
tell application "Messages"
     set status to offline
end tell
and that work correct
but when I try to set status to available or any else:
tell application "Messages"
     set status to available
end tell
then I haven't any results
what wrong?

Brian Smith5 wrote:
where whatever is the name of the service you're sending messages over. Not every messaging service has a status option, so I'm not sure that setting a global status has any meaning.
Where can one find the name of the service?
To get the names of the services, I used the following:
tell application "Messages"
          get every service
end tell
That returned three services: "Default" and two strings of characters.
I then tried your script:
tell application "Messages"
          set status of service "whatever" to available
end tell
I replaced "whatever" with each of the three services returned by the first script.
All three returned this error:
     Messages got an error: Can’t set service "[name of the relevant service]" to available.

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

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

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

EO Messages with Delivering Status in Adapter Engine

Hi All,
We have a scenario DB-DB Asy with Java Proxies. Proxies are there to accept the messages from Sender DB and insert in target DB. Get the response from target DB and insert back that to Sender DB.
Actually the scenario is Syn, but we made it as Asynchronous by implementing Java Proxies.
Now we are using EO mode in Sender JDBC channel. We have 17 interfaces in the similar pattern. We are using one common XI receiver channel for all these 17 interfaces.
If one message got struck, then rest other Proxies are not getting triggered and not able to resend the message ( ofcourse I know I cannot resend with Delivering Status). But not sure what causes the messages to failed with Delivering Status mode.
Any pointers would be highly appreciated.
Will increase of Parallel Queues really solve my problem? If it fails in Prod, its a big problem for us as we dont want to lose the data. Now everytime we are restarting the Message service server.
Regards,
Srinivas

Normally if there is any problem in target then you will see the adapter engine message as delivering
after the no of retires set then status will go to system error
during this entry check the CC used what is the error causing for that ?
HTH
Rajesh

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.

To Be Delivered Status for messages

Similar Messages

Maybe you are looking for