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

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!

  • Messages stucked in moni with queue status as "RUNNING"

    Hi All,
      Few of messages stucked in moni with queue status as "RUNNING" from the past 6 to 7 hours. all the stucked messages running on same dialog instance app server 03 (ucobpi03_PIP_03). i checked PIP appserver its working fine.
    Can any one please expalin me how to clean the queues..is there any effect of other queues ?
    Thanks,
    Siva.

    Hi,
    it can be due to multiple reasons....
    check the interface logic built ...it can be either due to this or can be of large volume of data...
    Also check the queues have been registered or not...
    HTH
    Rajesh

  • Messages are in to be delivered status

    Many messages are in to be delivered status in the adapter engine message monitoring
    Can any body help regarding this

    Hi Sandeep,
         Would you explain a little bit more your issue?
         i.e:
         This kind of messages are Sync Messages?
         Do you have more than one message in Interfaces Determination object?
         If multiple inbound interfaces are assigned by the interface determination, the messages are forwarded according to the quality of service Exactly Once in Order (EOIO) at runtime. This means that the order in which the inbound interfaces are entered in the interface determination determines the order in which the messages are received.
         You can change this default by deselecting the Maintain Order at Runtime checkbox. In this case, the quality of service Exactly Once (EO) is used to forward the message to the inbound interfaces.
    Regards,
    Luis Diego

  • Monitoring EOIO Messages stuck in AE with HOLD status?

    Hi Gurus,
    Scenario: IDOC -- > XI (Message split) - - > (HTTP/File)
    Some times messages to File adapter are stuck in Adapter Engine with status "HOLD". Found the root cause and un-checked "Maintain order at runtime" in interface determination.
    How to get alert if the EOIO messages are stuck in AE with status "HOLD"?
    Please help.

    Hi,
    HOLD status
    This is an EOIO message whose predecessor was not processed successfully yet. The status is retained until all predecessors are delivered successfully. If a predecessor has the "System error" status and is restarted, all successors are also restarted provided that the delivery of the predecessor is successful.
    If a predecessor has the "canceled with errors" status, further processing is not possible in systems before Support Package 11 for the adapter framework and Support Package 10 for the adapter framework core patch 02. In higher version systems, the status of predecessors can only be set to "canceled with errors" in a manual way. Successors that have the "Holding" status can be restarted after you have set the "canceled with errors" status (see related note 811864).
    Regards,
    Sreenivas

  • Trigger Alert E-Mail When messages were in To Be delivered Status

    Hello all,
    Is it possible to trigger an Alert E-mail if a message struck up in 'To be delivered' status ??
    I Know this status is not an error status with AE to trigger alert automatically. We are facing this problem often and when we restart XI AF messaging system, all messages were processed.
    We would like to know if messages were struck up with that status more than 15mins.
    Any thoughts??
    Regards

    Hi,
    Standard Alert Frame work will not support sending an Alert for To Be delivered status.
    you have to do some work around,
    check below blog and apply this design
    /people/shweta.walaskar2/blog/2011/05/12/trigger-alerts-for-messages-in-to-be-delivered-status-monitoring-adapter-queue-lock
    Regards,
    Raj

  • Message stuck in adapter engine with status Hold, how to delete those

    Hi,
    In Dev system around 6 lac messages are stuck in ;holding' state. How can I delete them. Is there is any standard proge which can delete all these messages.
    Can I delete messages of IE with status 'recorded'?
    Regards,
    Krishna

    Hi,
    see this wiki
    RSXMB_ARCHIVE_MESSAGES Archive XML Messages
    RSXMB_CANCEL_NOT_REST_MESSAGES Cancel XI Messages With Errors That Cannot Be Restarted
    RSXMB_DELETE_ARCHIVED_MESSAGES Delete Archived XML Messages
    RSXMB_DELETE_MESSAGES Delete XML Messages from the Persistency Layer marked for DEL
    RSXMB_CANCEL_MESSAGES Mass cancellation of error messages - XI
    RSXMB_SHOW_REORG_STATUS & RSXMB_SHOW_STATUS provide an overview for all XML messages in XI persistency layer.
    RSXMB_MESSAGE_STATISTICS2 which provides the processing statistics. This report basically analyzed the history table.
    RXWF_XI_UNSED_MSGS report helps in converting messages states other than 003 to final state i.e. 003.
    SXMS_REFRESH_ADAPTER_STATUS report helps in converting message sates like 001/008 into final state.
    http://wiki.sdn.sap.com/wiki/display/XI/PIArchivingConceptual+Overview

  • Messages stuck with green flag A. Status (XI 2.0)

    Hi All,
      we are running an instance of XI 2.0 and for this interface in particular we are pulling a file off an FTP server via the file adapter and pushing it through to a remotely enabled function which creates a batch session on our SAP R/3 4.6C instance.  The interface used to work but we have now changed the name of the function within R/3 then made the corresponding changes in XI.  Since we've done this the messages appear to be getting caught up somewhere between XI and R/3.  The XI monitor (SXMB_MONI) shows in the A. Status field a green flag.  To me this would imply that it is processing on the remote end (R/3) however there has not been any batch session created.  This flag remains green indefinately.
      I thought it could have something to do with XI caching some old objects so I ran tx SXI_CACHE and did a complete cache refresh (F6).  This did not change anything.  I have cleared all messages out of the queue using tx SM58.  Then after reading another post in this forum I ran tx smq1 and smq2 to clear messages out of there but there was nothing in those queues.
      When I push another message through it will sit in SXMB_MONI with the A.Status field having a green flag.  Then I look in tx SM58 and find that the status text field displays "Transaction executing" for a very long time.  Eventually it changes to "timout during allocate of registered program / CP" but the message is not going through.  The only thing that has changed has been the name of the function in R/3.
    any thoughts?

    Hi Mark,
      under the 'Target System' column in transaction SM58 it says "AI_RFCADAPTER_JCOSERVER".  When I test it out it seems to work fine ... no errors.
    When I looked at the trace labeled "Adapter_rfc.log" within the adapter engine it lists the following error.
    >>RfcAdapter> Tue Oct 11 07:46:12 CDT 2005>>
    > cannot load function template for Z_XI_INTERFACE_TEST1
    > exception occurred, detail:
    > com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: CPIC-CALL: 'C
    > MRCV'
    I'm not sure why we get this error.  The function template Z_XI_INTERFACE_TEST1 does exist and we were using it before.  If I run the interface again this error will no longer appear.  It almost seems like it will display only once a day.
    any other thoughts?

  • 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

  • Sender File channel in "To be Delivered" status always- PI 7.4- ICO interface

    Hello All,
    We are testing one Integrated Configuration Object (ICO) which is developed on PI 7.4 system (dual stack). Scenario is simple file to file and it doesnt have any ESR part (pass thru interface).
    Sender channel (File adapter NFS based) is picking the file from IN directory and after which it is always in "To be Delivered" status and it never passed to Receiver file channel (NFS based).
    We tried stop and starting the channel, deleted and recreated the channel, reactivated the channel, cancelled and restar the message from Message monitoring page, Cache refresh from ID and CPA cache refresh which didn't help us.
    Below is audit log of sender File channnel:
    Please help us in solving this problem.
    Thanks,

    Hi Naresh,
    Have you tried Eng Swee Yeoh advices in this blog Handling and preventing messages stuck in To Be Delivered status?, like to set timeout and the mode Per file transfer.
    Regards

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

  • Messages going in "To Be Delivered" Mode in RWB

    Hello Experts,
    Your urgent help needed...
    Right now i m suffering from a big problem....
    I m sending messages from SAP to Oracle via XI.
    for all the messages I am getting acknowledgement back... but if sometimes i will get acknowledgement as "Acknowledgement contains system error" then after that all the messages starts going into "To Be Delivering mode".
    After that i used to Restart the server itself and then after 2-3 hrs. suddenly all messages will go into success...
    Please tell me what might be the cause... and how to over come this problem...
    eagerly waiting for ur replies.........
    Please help me out in this problem as soon as possible... If any more clearifications are required then also tell me....
    I hv already checked SMQ1, SMQ2 but no messages are there....
    In SXMB_MONI it is showing all the messages as success but in RTW->MDT it is showing messages as "To Be Delivered"
    So please help me out with this.....
    Regards,
    Chaitanya.......

    Hi Jason,
    Have you received any reply regarding this issue? Is it fixed?
    We have also been experiencing this problem (for a week) with messages stuck in MDT RTW in status "Delivering", for first 20-30 messages and then eventually in "System Error" for the other ones. We keep re-starting XI (both stacks) to push the messages to IS, but need to find a real solution.
    SAP support has not been prompt to help, although we opened status high customer message.
    This is inbound transaction coming via RNIF 2.0  XI 3.0, not a new system; it has been running last two years.
    Will be grateful for any suggestions on how to fix this problem.
    I presume it is tunning issue, but where to start?
    Margaret

  • Messages are in Backlog without any status

    Hi All,
    Today morning when I came and observed that, in the Engine-Status page i saw some 3000 messages under column
    "Processing Backlog (without errors)". When I went into Messaging Overview Tab, I see these messages are in 'To Be Delivered' status. Now How to reprocess these messages? Can anyone tell me how come out from this situation?
    Regards,
    Rahul

    Hi Achaari,
    This is related to Queues problem.U r messages are struck in Queues.Please do following steps.
    1)Go to SMQ2.Then check ur queues.if u found any queues just select it and activate the queue.It will automatically sent the data.
    2)Go to SXMB_ADM->Manage Queues->Register Queues->Activate Queues.Before doing this activity in SXMB_ADM please delete or activate the queues in SMQ2 other wise it will give error.
    3)Cancel the System Error Messages in Adapter engine in RWB Message Monitoring.
    4)Refresh Cache Objects SXI_CACHE.
    Thanks
    Ravi

  • 'To Be Delivered' status in DAE; Issue with DAE?

    Hi,
    We have Decetral Adapter Engine (DAE) in DMZ. When we use DAE to drop file using receiver file/FTP adapter, we see all the messages are in "To Be Delivered" status.
    Sender file/FTP adapter is able to pick the file succssfully from the same location.
    Audit log has the following status:
    Success Message successfully received by messaging system. Profile: XI URL: http://sapxaqv:52100/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
    Success Using connection File_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
    Success Message successfully put into the queue.
    We tried to change all the parameters in receiver CC, still the same status as 'to be delivered' even after giving few wrong parameters to test (gave worng password didn't detect it).  Looks like it doesn't going beyond the queue to process.
    Thanks for your help in advance.
    Thank You,
    Indrasena Janga

    Hi,
    Generally "to be delivered" status messages cannot be changed to any other status directly  except by taking the restart of messaging service in the Visual Admin.
    Goto Visual Admin --> AF (Adapter Framework) services and take a restart of this particular service.
    J2ee Restarts sometimes helps but this aint a recommended or feasible option.
    Up gradation to SPS18 would be helpful to avoid restarts.
    Cheers
    Dhwani

  • 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

Maybe you are looking for