TBDL messages in IE

Hi All,
How to delete or cancel TBDL messages in Integration Engine (IE).I deleted all the workitem for the corresponding TBDL messages still I can see few messages in TBDL in Message monitoring .
Please suggest what to do to delete at database level or cancel these messages
Thanks in Advance

Vidya,
Is your system configured as HA ?
Do you frequently see messages in To Be Delivered status ?
Do you notice messages in tbd for all interfaces or for interfaces using a specific adapter type ?
tbd is generally caused by insufficient threads or by blocked threads in the MS.
Did you check the thread usage ?
I have seen that restart of the j2ee always helps in such cases or you can try by restarting the XI AF messaging service.
I think it would be better if you open a message with SAP so that they can find out the root cause.
Regards,
Sumit Khetawat

Similar Messages

  • SAP PI/PO 7.31 - Single Stack - Best way of handling 'TBDL' messages

    Hi All,
    I would like to know what is the best way of processing 'TBDL' messages that are shown in 7.31 message monitoring.
    One way I know is to resend the messages but if the volume is huge (100k+), is there a strategy to reprocess them automatically by creating a Job? AFAIK, a job only picks NDLV messages for reprocessing.
    Please share some information on handling such scenarios.
    (PS: I've been through many links with TBDL issue but strategy wise, could not find any concrete responses. One of them suggested cancelling all using SQL command. I would like to know if there are some other ways.)
    Thanks,
    Abhishek

    Hi Abhishek,
    1. TBDL message are handled automatically by the system. Is there a specific time frame(or any setting) under which they start getting delivered automatically? Or it waits for resource/thread recovery?
    - TBDL is an intermediate message status. Depending on the number of queues/threads for this adapter type, you will also have 5/10 messages in Delivering status. Something is preventing these messages from being delivered and this results in the backlog of messages in TBDL status. Only when the messages in Delivering status are processed will the threads be released and then become available for the messages which are backed up in TBDL.
    2. If messages remain in TBDL for a longer time than expected(like 3-4 days), is there a way to resend them? Any job configuration that can do this?
    - There is no way to resend TBDL messages. As above, this is an intermediate status. The focus should be on the messages in Delivering status and why these are not reaching their target and thus freeing up the threads for the backlog.
    3. I would like to understand what factors on sender/receiver side can cause this to happen? Any supporting/clarifying documents? (1808554 is already analyzed and we are on a higher patch level)
    - It is very difficult to answer this. There could be many different factors which could cause this to happen. Receiver system may not be available, network issues, bugs on SAP side etc. It really depends on the individual case. Best practice here would be to ensure any timeout settings are configured for the relevant adapter types. This can help prevent issues.
    4. Changing message status at DB level is advisable or not? If yes, then setting them to NDLV and reprocessing using a job is suggested?
    We do not advise to make any changes to message status at DB level. This option should only ever be used as an absolute last resort.
    Ultimately the best way to get to the bottom of this is capture Java Thread dumps and create a support ticket with SAP.
    Regards
    Mark

  • Messages are in "To Be Delivered" state

    Quite many times has happened that several messages have been stucked in XI 7.0 Production system in status "To Be Delivered".
    Resending stucked messages is not possible.
    The solution for issue is to restart Java stack.
    But This is not permanent solution to restart Java stack of production system every time.
    Please guide me to resolve this issue.

    Hi Rohan,
            In the Adapter engine message monitoring please enable the serialization context and check is there any old message is in error or holding or waiting status.
              If there is any please cancel them and resend the TBDL message.
    Thanks and Regards,
    Murugavel S

  • Message to be delivered RTWB

    I have a straight forward HTTP - > RFC interface. The end user states they are getting a HTTP 500 error. It's as if the process has been cancelled/aborted. This processing has been working for the past month without incident. Nothing has been changed.
    Checking SXMB_MONI I can see a small grey dot next to the message. Checking RTWB it's status is 'To Be Delivered'. I've checked SMQ1/SMQ2 and there is nothing queued.
    Where else can I check to see what caused the failure. Is there anyway I can recover the data the message should have returned from SAP. I can't see anything in RTWB.
    Many thanks

    Hi,
    I have faced the same situation.
    First  Restart the communication channel and then try to resend the TBDL message.U can.
    if again you are facing the problem then you need to  restart the Java engine.
    For that run T-code SMICM go to Administrator> java soft >with Restart.
    Again if this will not solve ur problem then what i did just restart the server.
    We have called the SAP people and they have installed the SP16 patch. to sort out this problem.
    Regards,
    Sumit Gupta

  • Adapter Engine Queue

    Hi.
    I got yhe following error in default trace.
    ==========
    Could not get next EOIO QueueMessage from MessageStore. Reason: com.sap.aii.af.ra.ms.api.MessagingException: Error retrieving message from database store. Reason: Could not create Message. Reason: com.sap.aii.af.ra.ms.api.MessagingException: Could not parse XMBMessage due to Binary index out of range: 1613824 Putting message back into sequencer for manual retry.#
    #1.5
    ==========
    I check the
    http://<host>:<port>/MessagingSystem/monitor/systemStatus.jsp, and found the following information.
    ?EOIO   Status   HOLD  -> 1
    ?????????   TBDL  -> 1
    ?Matrix  one of the Adapter
    ???????????TBDL -> 6
    ???????????Size -> 161384
    I think the Adapter Engine queue size is overflow.
    (It is 161384).
    Question1
    How can I restart this "TBDL" message?
    I tried to restart from RWB -> message monitoring,
    but could not deliver cause of error.
    Question2
    How can I change the "queue size"?
    There are documents that refer to "thread count",
    not but "queue size".
    The thread count is default. It's "5".
    best regards,

    Thank you for your replying.
    I retry the message, but the error occured again.
    I check this message by performance monitoring on RWB.
    Nomarry this inerface process the "5 messsages" at one time.
    The average message size is "2MB".
    The "TBDL" message size is 2MB(I mean average size),
    but the number of the message is "19"!!
    Should I increase the number of threads?
    regards,

  • Message split via BPM Status stays TBDL

    Hi to all,
    I have a Scenario with a BPM.
    In the IntegrationProcess (IP_Split), is a mapping with message splitting.
    The result von the Mapping are serveral Proxymessages and a var count, that counts the new Messages.
    After, i have a loop over the messages an with the receiverdetermination i send the new messages to the SAP-System.
    the Scenario works fine. in SXI_MONITOR it looks great.
    There is only one Problem:
    When i go to the Integration Engine in the Message Monitoring (Runtime Workbench) there is a strange Message.
    There is a Message with SenderService and ReceiverService IP_Split. The Status is still TBDL.
    Can anybody help me?
    Thanks
    Chris

    Hi,
    Few months ago we had also problems with "locked user" in XI, in our case XIAPPLUSER was sometimes (b)locked.
    Perhaps note:
    721548 Changing the passwords of the XI 3.0 service users
    will help you.
    We removed and entered the service users again, with the password in CAPITALS and language blank.
    After that our problem was solved, I hope yours too.
    Regards
    Jack

  • Message sutck in TBDL in Adapter Engine

    Hi all,
    We use RequestResponseBean and ResponseOnewayBean in the conversion from Async RFC to Sync SOAP.
    There was a big message load on this integration this morning. In the Adapter Message Monitoring, I found thousands of messages stuck in TBDL status. I checked in SMQ1 and SMQ2, there are no stuck queues.
    Anyone knows the problem.
    Thanks!
    Regards,
    Hui

    hi,
    I think there is some configuration error with the corresponding communication channel.

  • Error in file receiver channel "Unknown payload format 0 in the message"

    hello
    there is an errror in my receiver file channel with the status "Unknown payload format "
    my channel is file receiver channel.
    we implemented one sap note 1295430 and after that channnel is giving the error.
    Please forward your views.
    thanks.

    Hi there,
    First of all, what TBDL means - It means that the message was successfully delivered from Integration Server and that the messages are handed over to the Messaging System.
    TBDL occurs when the message is put into the receiving queue of the Messaging System.
    What can be done?
    Go to Messaging System receive servlet:
    http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>/<PROTOCOL>
    If this was executed successfully, then the MS returns HTTP 200 to the Integration Server and the status TBDL moves to DELIVERING (check whether you have authorization to go to the above link).
    --> Log-in to SAP using - XIAPPLUSER & XIAFUSER, and check if they are blocked
    --> Check the messages:
    AF
    com.sap.aii.adapterframework.serviceuser.language
    com.sap.aii.adapterframework.serviceuser.name = XIAFUSER
    com.sap.aii.adapterframework.serviceuser.pwd
    AS
    com.sap.aii.applicationsystem.serviceuser.language
    com.sap.aii.applicationsystem.serviceuser.name = XIAPPLUSER
    com.sap.aii.applicationsystem.serviceuser.pwd
    Also, worth reading - /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
    Let us know if you have more questions.
    regards,
    Neetesh

  • Clearing JAVA Message Queue in PI 7.1

    Hi Experts
    I am working on a file to File Scenario, and file has been picked up on the sender CC and mesaages have been sent to JAVA queues, But the messages are stuck on the JAVA queues,
    Java Queue name: File_http://sap.com/xi/XI/SystemRecv
    How can I clear the JAVA message queue in PI 7.1
    Thanks
    PR

    If the messages are on the queue, usually one of the actions must be performed: a) Fix the related scenario and restart the messages or b) Manually cancel the messages. This is also advised on the note below under item "3. Troubleshooting Archiving / Deletion in the Adapter Framework"
    [Note 872388 - Troubleshooting Archiving and Deletion in PI|https://service.sap.com/sap/support/notes/872388]
    If you are having performance problems, please check if the messages are taking long time in TBDL/Holding status. Let us know if this is the case.

  • How to clear the message which are in scheduled Status in PI 7.3

    Hi,
    We want to clear/cancel the message in Message monitor which are in scheduled status in PI 7.3.
    It only a JAVA Stack System , We have been trying to  clear the message manually but it take more time resulting into performance issue.
    Is there some other way we can clear it from Database level.
    Our Database is Db2 9.7 with Fix Pack 5
    Can anyone help me in clearing the message at fast speed ?
    Thanks in advance
    Amit Shedge

    Hi,
    First we check the status of Message
    a) db2 => select count(*) COUNT, status from sap<sid>db.bc_msg group by status
    COUNT STATUS     
    110        DLVD       
    641623   NDLV       
      2 record(s) selected.
    Then we update the status of Message to Failed
    b) UPDATE BC_MSG SET STATUS='FAIL' WHERE STATUS IN ('DLNG', 'TBDL', 'WAIT', 'HOLD', 'NDLV')  AND SENT_RECV_TIME <= '2014-22-03 00:00:00'
    c)
    select count(*) COUNT, status from sap<sid>db.bc_msg group by status
    COUNT STATUS     
    183      DLVD       
    641623 FAIL       
    d) Then we started the Standard deletion Job in NWA
    db2 => SELECT COUNT(*), STATUS FROM SAP<sid>DB.BC_MSG GROUP BY STATUS
    1 STATUS     
    98 DLVD       
    And the message got deleted.
    Thanks & Regards
    Amit

  • 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

  • Troubleshoot-Adapter engine:Error Setting the message status to DLNG failed

    Dear Experts,
    We use SAP RFC- PI-JDBC(MSSQL).  here the Data(message) successfully transfered to mssql table but the status is been set to DLNG failed,  And it finally shown as SYSTEM ERROR.
    QoS required: ExactlyOnce ,  here The Message has got inserted in that particular table and in PI adapter the  status turned to  DLNG faild and the service again tries to send the same message which is not possible becoz the data is set for primary value.
    2010-09-15 09:59:48 Success Message successfully received by messaging system. Profile: XI URL: http://XXXXX:50000/MessagingSystem/receive/AFW/XI Credential (User): YYYY
    2010-09-15 09:59:48 Success Using connection JDBC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
    2010-09-15 09:59:48 Success Message successfully put into the queue.
    2010-09-15 09:59:48 Success The message was successfully retrieved from the receive queue.
    2010-09-15 09:59:48 Error Setting the message status to TBDL failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: Error updating status..
    2010-09-15 09:59:48 Success Delivering to channel: CCR_JDBC_ZZZZZ
    2010-09-15 09:59:48 Success MP: Entering module processor
    2010-09-15 09:59:48 Success MP: Processing local module localejbs/CallSapAdapter
    2010-09-15 09:59:48 Success Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
    2010-09-15 09:59:48 Success JDBC adapter receiver channel CCR_JDBC_ZZZZZ : processing started; party  , service BS_BCP_IMPLOG_ZZZZZ 
    2010-09-15 09:59:49 Success Database request processed successfully
    2010-09-15 09:59:49 Success MP: Leaving module processor
    2010-09-15 09:59:49 Success The message was successfully delivered to the application using connection JDBC_http://sap.com/xi/XI/System.
    2010-09-15 09:59:49 Error Setting the message status to DLNG failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: Error updating status..
    2010-09-15 10:37:01 Success The message was successfully retrieved from the receive queue.
    2010-09-15 10:37:01 Success The message status set to DLNG.
    2010-09-15 10:37:01 Success Delivering to channel: CCR_JDBC_ZZZZZ
    2010-09-15 10:37:01 Success MP: Entering module processor
    2010-09-15 10:37:01 Success MP: Processing local module localejbs/CallSapAdapter
    2010-09-15 10:37:01 Success Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
    2010-09-15 10:37:01 Success JDBC adapter receiver channel CCR_JDBC_ZZZZZ : processing started; party  , service BS_BCP_IMPLOG_ZZZZZ
    2010-09-15 10:37:01 Error Unable to execute statement for table or stored procedure. 'imp_log' (Structure 'STATEMENT') due to com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'PK_XXX_log'. Cannot insert duplicate key in object 'dbo.XXX_log'.
    2010-09-15 10:37:01 Error JDBC message processing failed; reason Error processing request in sax parser: Error when executing statement for table/stored proc. 'imp_log' (structure 'STATEMENT'): com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'PK_XXX_log'. Cannot insert duplicate key in object 'dbo.XXX_log'.
    Thanks in advance for your valuable answer.

    Hi Vinaygam,
    2010-09-15 10:37:01 Error Unable to execute statement for table or stored procedure. 'imp_log' (Structure 'STATEMENT') due to com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'PK_XXX_log'. Cannot insert duplicate key in object 'dbo.XXX_log'.
    2010-09-15 10:37:01 Error JDBC message processing failed; reason Error processing request in sax parser: Error when executing statement for table/stored proc. 'imp_log' (structure 'STATEMENT'): com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'PK_XXX_log'. Cannot insert duplicate key in object 'dbo.XXX_log'.
    See above error, It cannot the Duplicate Key in your log table. Duplicate means repeated as a same data.So kindly check once your data.
    IF,I assume your scenario is Synchronous, If you are using any sender JDBC adapter  just check with your Quality of Service and set it to "Exactly once".
    so kindly do it.
    Thank you,
    Sateesh
    Edited by: sateesh kumar .N on Sep 17, 2010 8:17 AM

  • Distributing message type COND_A using ALE

    Hello everybody,
    I am distributing purchasing info records using ALE (transaction ME18). This works fine.
    Now I also want to distribute the corresponding conditions.
    I know that I need an additional message type COND_A. I created the new message type in BD64.
    But I don't know how to trigger the distribution. I cannot find a transaction for distributing conditions and they won't come along when I distribute the info records.
    Any help would be appeciated.
    Thanks
    Roland

    Hi Roland,
    It is quite tricky. But it worked well for me.
    Please choose the pricing report (t/code V/LD) which meet your criteria extraction and copy the report program into custom program.
    Let's say you copy report program <b>/1SDBF12L/RV14AK15</b> (Material Price) into <b>ZRV14AK15</b>.
    Then you need to modify selection screen of ZRV14AK15 program to enable the sending IDoc parameters as follows.    
    *PARAMETERS sen_idoc(1) TYPE c NO-DISPLAY.
    *PARAMETERS getknumh(1) TYPE c NO-DISPLAY.
    *PARAMETERS p_delete(1) TYPE c NO-DISPLAY.
    *PARAMETERS p_mestyp  LIKE tbdme-mestyp  NO-DISPLAY.
    *PARAMETERS p_logsys  LIKE tbdls-logsys  NO-DISPLAY.
    PARAMETERS sen_idoc(1) TYPE c DEFAULT 'X'.
    PARAMETERS getknumh(1) TYPE c NO-DISPLAY.
    PARAMETERS p_delete(1) TYPE c NO-DISPLAY.
    PARAMETERS p_mestyp  LIKE tbdme-mestyp DEFAULT 'COND_A'.
    PARAMETERS p_logsys  LIKE tbdls-logsys OBLIGATORY.
    Now you should be able to use this custom program to generate IDoc for message type COND_A.
    Please ensure you have setup the ALE and IDoc configuration such as distribution model (BD64), partner profile (WE20), IDoc Ports (WE21) and etc.
    Hope this will help.
    Regards,
    Ferry Lianto
    Please reward points if helpful.

  • Message already in admin action

    Hello,
    One EO message is stuck (TBDL) in single stack PI version with below error, i thought removing user lock (from NWA -> User Sessions) will work and release the locks from the message but it didn't work.
    Resending the message failed, due to: java.lang.Exception: Message already in admin action or locked by message version editor.
    Not sure what else i can check? Any inputs will be appreciated.
    Thanks
    Amit Srivastava

    Hi Amit,
    So you did remove the locks under NWA-> Locks: Java Locks?
    If that didnt work. I would suggest you stop the receiver channel and force the message into error. Did you also add a timeout on that channel?
    The thing is what i have picked up with TBDL is that once it is stuck it is very difficult to get it going again. I normally force it into error(Restart the java stack or stop the channel untill error) and then i reprocess it. But i understand that would be your last options.
    Hope it helps,
    Jannus Botha

  • How to delete/cancel files stuck in To Be Delivered (TBDL) status

    hi all,
    i just want to ask how to delete or cancel files that are stucked in To Be Delivered (TBDL) status in RWB? i have cleared both SMQ1 and SMQ2 and even performed a full system restart, but the files are still there. can anyone please shed some light with this issue? it will be deeply appreciated. thanks!
    Edited by: dwinXG on Jun 9, 2010 5:36 AM

    Hi,
         Normnally Message status goes to ToBeDelivered if there are no more queues available for that particular adapter queue..
    so here first you need to check the messages which are in DLNG status and the logs/reasons behind them...
    Normally you cannot delete the messages in ToBeDelivered...but give a try going to RWB and filter the messages with TBD..
    and try ot delete there...
    But I prefer for the rootcause causing the messages to be delivered as the reasons can be target system might be down..or restarted which made the particular adapter queue hung..so chk it out..
    HTH
    Rajesh

Maybe you are looking for