Delete records in status holding on Adapter Engine

Hi all
We are running on XI 3.0 and Netweaver 04 with SP20 installed
I had a problem with a lot of message in status holding on Adapter Engine (develoment system)
I'm not able to restart (resend) or delete this message. I had look around on SDN and in SAP notes, and only found a lot of old stuff, but nothing there can solve my problem
This are a snapshoot of the error log
Success Processing child message of multi-message with message ID 3aa40608-c251-4845-209c-d327ba444b7c
Success Using connection JMS_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
Success Message successfully put into the queue.
Success The message was successfully retrieved from the receive queue.
Success The message status set to HOLD.
Success Admin action: Trying to redeliver message.
Success The message status set to TBDL.
Success The message was successfully retrieved from the receive queue.
Success The message status set to HOLD.
Success The message status set to TBDL.
Success The message was successfully retrieved from the receive queue.
Success The message status set to HOLD.
Success Admin action: Trying to fail message.
Error Admin action: Setting the message status to 'failed' failed, due to: java.lang.Exception: Predecessor not in final state.. Success Admin action: Trying to redeliver message.
Success The message status set to TBDL.
Success The message was successfully retrieved from the receive queue.
Success The message status set to HOLDError Admin action: Setting the message status to 'failed' failed, due to: java.lang.Exception: Predecessor not in final state..
Success Admin action: Trying to redeliver message.
Success The message status set to TBDL.
Success The message was successfully retrieved from the receive queue.
Success The message status set to HOLD
Kind regards
Kim

Hi,
Change the combination in message monitoring, this time chose Ingegration Engine & Database combination and if you have messages in holding then try to cancel them but first find and delete the system error messages if any.
If you get success here then change back the combination to Adapter Engine & Databse and then try to delete it again.
I am sure that it is possible coz same problem was there with me and then after doing some R&D I was able to delete them.
Regards,
Sarvesh

Similar Messages

  • Seeing old deleted comm. channels on Non-Central Adapter Engines

    hello,
    We have a landscape of PI 7.0 machine connected with 3 Non-Central Adapter Engines installed on another machine, which generally works fine.
    Somehow, after doing a lot of changes in the integration directory (creating and deleting object: scenario, comm. channels and ect...)  -  two of the non-central AE shows comm. channels which were already deleted (and activated ofcourse) in the integration directory.
    What i tried already:
    run CPACache in mode=full on each of those AE, clear SLD cache and even restarted those J2EE instances. but it didn't work out. the thing that is also weird is that I can start/stop those old comm. channels. how do we get rid of those old channels?
    I would appreciate any suggestions .

    Problem is solved.
    In integration directory we could not see the old comm. channels under the objects tab or under any scenario, but they existed as shown in RWB.
    From CPA cache we picked up the comm. channels object IDs and search for it in integration directory UI, once they were found - it was easy to actually delete them.
    What went wrong?
    These old comm. channels were assigned under deleted services which were under deleted parties. For some unknown reason, after deleting the services and parties successfully, the comm. channels underneath were not deleted and could not shown in any of objects tab GUI tree's nodes.
    We could not reproduce this behaviour.

  • Purging EOIO messages with status "Holding" at the adapter level in XI.

    Hi,
    I want to purge a set of messages (some 800) with status "Holding" at Adapter level in RunTime Workbench. I have gone through the blog "/people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework which explain the way to reprocess the messages which are stuck in EOIO so that the rest in queue are processed but is there a way to purge a large number of messages in a EOIO queue which are holding for long, at the adpater framework level thorugh some option in Runtime workbench or Visual Administrator of J2EE server on which XI is running ?

    Hi Gourav,
    What do you mean by delete files from folder.
    I have this problem and I can't get rid of the messages that are stuck in the adapter engine. 
    If I need step 3.  how is that done?
    Thanks.

  • How to process stucked holding messages in the Adapter Engine.

    Hi experts,
    This question is may be familier to all...
    There are thousands of messages are in holding status in the Adapter engine in RWB.
    I tried to found system error in these messages. There is no system error from the last in my investigation. I tried to restart of the communication channels of the combination of these messages. But it is also not use to fix this problem.
    Instead of the restart of the Java engine please let me know is there any possibility to fix this issue.
    Regards
    Mahesh

    Hello Mahesh
    You can try restarting some of the XI services (e.g. com.sap.aii.af.svc) but usually a java restart is required to free up these blocked threads/queues.
    Most likely these messages are in Holding status because there is a blockage in one of the Adapter queues. This can be monitored in the RWB
    -> Component Monitoring                                                
    -> Adatper Engine XIP                                                  
    -> Engine Status                                                       
    -> Additional Data   
    Find out what adapter queues are causing the blockage and increase the number of threads/queues available to it. This will help prevent the issue occuring again.
    See note #791655 Documentation of the XI Messaging System Service Properties, for an explaination of the queues.
    See these blogs for more details:
    1) /people/kenny.scott/blog/2007/08/20/messaging-system-queue-properties-after-xi-30-sp19-xi-70sp11
    2) /people/kenny.scott/blog/2008/12/05/xipi-file-and-jdbc-receiver-adapter-performance-and-availability-improvements
    Ensure note #937159 XI Adapter Engine is stuck, has been applied. 
    Regards
    Mark

  • Messages goes into scheduled status in adapter engine

    Hi all
    we are doing idoc to file scenario with direct mapping. the messages are getting processed in integration engine sucessfully. the messages are getting into scheduled status in the adapter engine even when there is less load in the server.
    Thiis specially happening for IDOC to file scenario only.  Any help is highly appreciated
    Thanks

    >
    > the system is quite good at the moment but the some of the messages again into scheduled status like ( 10 out of 1000 messages ) . the system is not performing at 100 % rate since some messages moves to scheduled status.  Is still the performance can be improved in any other ways ?
    >
    This is really strange behaviour , If Communictaion channel functioning correctly then all succesfull messages should deliver to Receiver system.
    Better to check payload of scheduled messages(if wrong payload obiously it goes schedule status),try to to reprocess them.
    I never used XCOPY command,so no comment on that.
    Regards,
    Raj

  • Adapter Engine Prioritation for JDBC Adapter

    Hi ,
    I am currently working on an Idoc to Jdbc Scenario. The jdbc adapter is used to push the messages to three different legacy systems through three different scenarios. I need to prioratize the messages of the legacy systems(For Eg. Legacy System A is more critical than Legacy System B) in adapter engine or in adapter itself.
    Regards,
    UserPI

    Hi
    We are having the same problem. Once one of the interfaces which is using a JDBC communication channel is processing a bigger amount of messages, the JDBC adapter seems to be blocked exclusively for that interface. All other interfaces using the JDBC adapter are on hold (status "Scheduled" in Adapter Engine Message Monitoring). I set up message prioritization in RWB (Component: Adapter Engine), but it doesn't help (nothing different from before).
    Does anybody has a hint on that?
    Thanks
    Philippe

  • Adapter engine in CC

    we chooose adapter engine as ntegration server in PI 7.0 and we go with adapter engine as central adapter engine in PI 7.1..
    is this b cos 7.1 has advanced adapter engine?
    can u pls clarify?

    Hi Ravindra,
    Advanced Adapter Engine:
       Advanced Adapter engine is just  a normal adapter engine but  in PI7.1 terminology.SAP  named it so,because of the additional features that have been added to Adapter engine PI7.1 .
    http://help.sap.com/saphelp_nwpi71/helpdata/EN/8f/d906d01f77fa40a4c84683c3f8326f/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/EN/8f/d906d01f77fa40a4c84683c3f8326f/content.htm
        and as far as the Central adapter engine is concerned ,The Adapter Engine is a separate software component that is automatically installed on the Integration Server. In this case, it is the central Adapter Engine. However, you can also install the Adapter Engine separately on another host. This is then a non-central Adapter Engine.
            So Advanced Adapter engine has nothing to do with the Central Adapter engine that  you saw in file to file scenario article which is based on PI7.1 Even Advanced Adapter engine is also a very interesting feature introduced in PI7.1 so that Adapter engine it self does some Integration Engine functions.If you find time listen to the webinar recorded session on AAE (Advanced Adapter Engine).
    http://www.sdn.sap.com/irj/scn/elearn?rid=/library/uuid/b08af1f4-5615-2c10-a3ab-990f7cd0b5ac&overridelayout=true
    Hope you are clear with your question.
    Thanks,
    Ram.

  • Message struck in adapter engine with status Hold

    Hi,
    In intergaration engine all messages are processed, I have checked SMQ1, SMQ2 (no message is struck in queue)
    where as messages struck in adapter engine with status Hold, I have checked this in RWB. How to resolve this?
    Regards,
    Krishna

    Hello,
    Below is some information on how to resolve this type of issue:
    1 - In the RWB, expand the tray for "Configure Table Columns" - by clicking on a square at the right end of this heading.
    2 - Check the checkboxes for "Serialization Context" and "Sequence Number". These should then appear in the table columns as well.
    3 - Add the Serialization Context to the Extended Filter Criteria. Search the messages in status HOLD based on this new additional criteria.
    4 - Sort the messages in ascending order based on the Sequence no.
    5 - Check the predecessor message of the first message in status "HOLD"
    Based on the following status for this predecessor messages, the actions that can be taken for the HOLD messages are:
    a - Predecessor is in Failed State/System Error : Cancel/Resend the
    first message in status HOLD after this. Then the remaining messages
    can be cancelled/resent.
    b - Predecessor is in DLVD state(delivered state) : First Holding
    message can be resent/cancelled followed by the others.
    c - Predecessor is in NDLV(Non-Delivered Status) : Check why the
    predecessor message failed and correct the reason for the failure.
    Then resend the predecessor message and then cancel/resend the
    remaining HOLD messages. Alternatively, you can directly try
    resending this NDLV predecessor message and see if it goes. If it
    goes, then the remaining HOLD messages can be resent/cancelled.
    Another option could be to cancel this NDLV predecessor message so
    that it goes to FAILED state and then cancel/resend remaining HOLD
    messages.
    Regards,
    Sarah

  • Status "HOLDING" in RWB----- MessageMonitoring------ Adapter Engine?

    Hi Experts,
    I am working on a IDOC to file Scenario.
    Sometimes the scenario works perfectly and the files are generated successfull
    Somtimes the status of the messages are "HOLDING" in  RWB--->MessageMonitoring---->Adapter Engine(Messages from the component)?
    Why is this inconsistency ? What may be the reason.?
    Thanks in Advance,
    Anil

    HI,
    Holding state says that your QOS is EOIO.
    If any message is not processed  successful,
    then next all message is all holding state.
    Go throgh this link how to handle these messages
    How to deal with stuck EOIO messages in the XI 3.0 Adapter Framework
    Regards
    Sridhar Goli

  • How to delete / cancel messages in PI adapter engine

    Hello expert,
    we have a scenario File (EOIO) --> PI --> ABAP. Today the file we received is big (>100mb), apparently PI can't handle it, and we got error
    Transmitting the message to endpoint http://host:port/sap/xi/engine?type=entry using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException:
    Error transmitting the message over HTTP. Reason: java.io.IOException: Error writing to server.
    seems like PI adapter engine got problem while delivering the huge message to ABAP integration engine. In RWB message monitoring, the message is set to Error. Unfortunately the file has been picked up many times, thus the huge message is stuck in adpater engine. In RWB message monitoring, I can see the message listed many times and status is HOLDING because the previous message can not be delivered to Intergration engine. I want to delete/cancel all the messages, I tried in RWB message monitoring to cancell the messages, however after cancelling one message, it crashed the PI system and cause a reboot.
    My question is; Is there some place in NWA (net weaver admin) to force all the messages to be deleted? (Because deleting/cancel in RWB message monitoring does not work because it causes system crash).
    Thanks
    Jayson

    Hi Team,
    I couldn't able to delete old message's from one of Q system, Persistence layer is 584 % filled, after triggering delete job(RSXMB_DELETE_MESSAGES) and Persistence layer has come to 384% and further I couldn't able to delete old messages.I executed program "
                                                                                                          RSXMB_CHECK_MSG_QUEUE" and manage  to delete few entries.Could you please suggest how to reduce fill level to below 100%
    Switch Procedure (for Persistence Tables) Deactivated
    Number of Table Entries                                                           
    3.185.992
    Maximum Number of Table Entries                                                   
    830.000
    Current Fill Level in %                                                           
    384
    Threshold value for fill level for executing a switch run in %                    
    60
    Number of Logically Deleted Table Entries                                         
    0
    Decline of Fill Level in % Following Deletion                                     
    384
    Delete or archive processed XML messages
    Job log overview for job:    SAP_BC_XMB_DELETE_001 / 06302000
    Date       Time     Message text                                                                               Message class Message no. Message
    13.03.2013 06:39:55 Job started                                                                                     00           516          S
    13.03.2013 06:39:55 Step 001 started (program RSXMB_DELETE_MESSAGES, variant &0000000000034, user ID SAPBATCH)      00           550          S
    13.03.2013 06:39:55 Value for parameters DELETION-RELATED_OBJECTS-ASYNC: 1                                        XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-RELATED_OBJECTS-ROWS: 100                                       XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-RELATED_OBJECTS-IDX5_DELAYED: 0                                 XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-ROWS_PER_LOOP-DELETE: 100                                       XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION-ASYNC: 007                                     XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION-SYNC: 007                                      XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_ERROR-SYNC: 007                                XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION-IDX5: 007                                      XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_UNIT-ASYNC: D                                  XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_UNIT-SYNC: D                                   XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_ERROR_UNIT-SYNC: D                             XMS_ADM        375          S
    13.03.2013 06:39:55 Value for parameters DELETION-PERSIST_DURATION_UNIT-IDX5: D                                   XMS_ADM        375          S
    13.03.2013 07:27:58 0 XML messages deleted                                                                        XMS_ADM        351          I
    13.03.2013 07:27:59 Step 002 started (program RSXMB_TABLE_SWITCH, variant &0000000000034, user ID SAPBATCH)         00           550          S
    13.03.2013 07:28:00 Job finished                                                                                    00           517          S

  • Message status "Holding" - Message monitoring adapter framework

    Hello,
    We have some messages with the status "Holding" in a queue in the message monitoring in the adapter framework.
    Normally you have to restart the first message of that queue. The message with the status "system error". Unfortunately this message is not available anymore because it is older than 30 days and the retetion period is 30 days.
    I already read the blog about "[How to deal with stuck EOIO messages in the XI 3.0 Adapter Framework|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417100)ID1887311350DB01819286872323159351End?blog=/pub/wlg/3566]"
    The blog does not mention what to do when the first message (sequential number) is not available anymore.
    Is it possible to restart the messages in the queue in that case?
    Thanks
    Kind regards
    Frank

    Unfortunately this message is not available anymore because it is older than 30 days and the retetion period is 30 days.
    I assume that the message was deleted.....in this case the next message in the queue will be blocking the queue....so try resending this message....even the blog mentions that you either solve the error or cancel the message....so now start from the second message....if possible solve the error for this message....if not possible to resolve then cancel it so that rest of the queue gets processed
    From the blog:
    Now the erroneous message is the first message in the display. You can look at the error reason, try to fix the problem and
    resend or cancel the message to release the queue.
    Regards,
    Abhishek.

  • Messages are in hold in the Adapter Engine

    Hi all,
      I am seeing in my adapter engine that all of the messages are in status hold , it is for  a specific business system and interface.
    2009-02-10 21:41:30 Success Message successfully put into the queue.
    2009-02-10 21:41:31 Success The message was successfully retrieved from the receive queue.
    2009-02-10 21:41:31 Success The message status set to HOLD.
    can anyone please help?
    Thanks in advance
    Sugata B

    Hi
    i ve got the same problem .
    I m using the message monitor in order to find the first message in error in this queue and so to be able to free the queue.
    My problem is how to detect these holding messages.
    As the error is in the Adapter Engine , you cant see it in sxmb_moni transaction
    In the message monitoring, you can check it manually.
    I need to have an automatic report of 'holding messages".
    I try to connect the Adapter engine alert to the ccms. The problem is that autoreaction alert arent possible in this case.
    Any body found the means to check directly in the database with sql-based command the status of message ?
    thanks for your help
    florent

  • 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

  • Cancelling/Deleting messages in the adapter engine

    Hi Everyone:
    How can I cancel or delete a message in status 'system error' in my adapter engine.
    I do not want this message will be resent by mistake when the receiver comm chanel will be active.
    Thanks a lot guys.

    Alvaro,
    If the message is successfully processed then you cannot delete. If your message is in waiting or etc. then go through this weblog for much information:
    /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
    Hope this helps you...
    ---Satish

  • Deleting Records based on status in another table

    Dear All,
    I am using oracle 11gR1 on Linux.
    We have two tables one holding year starting and closing dates with year status as open/closed for multiple years and multiple entities. Any year may be open for an entity.
    Relevant columns/Pk
    PK: entity_id, fin_year_id
    Cols: year_st_dt, year_end_dt, year_status
    We have another table where monthly summarized information is stored via scheduled procedure. Currently the procedure deletes all records and inserts new records.
    Relevant columns/Pk
    Cols: entity_id, year_month
    What we want is that the procedure should not delete records that related to financial years that are closed.
    How would I write a delete statement to do that?
    Regards, Imran

    Hi,
    957 posts, but still while posting a question, you have not
    1) Posted the table structure of all the tables involved. (create statement)
    2) Posted the sample input (insert statement)
    3) Posted the sample output.
    4) More importantanly posted on the correct forum.
    Regards
    Anurag Tibrewal.

Maybe you are looking for