Message got struck in hold status in message monitoring.

Hi SDNers,
             I am doing Idoc to File scenario. I triggered an Idoc and it is successfully processed in XI and got struck in message monitoring with hold status.
             After repetetive attempts of restarting the message, still it is in hold status.
             Even if I tried to cancel the message, it is not cancelling as it is in hold status.
            Can anybody please help how to process the message or can anybody explain how to cancel the message from message monitoring, which is in hold status.
Regards,
Jayaram.G

Hi,
If the message that has not yet been delivered is not in error state, the problem cause is probably that the message is blocked in the QRFC queues of the Integration Engine.
Check queue status
Call the Integration Server and call transaction SMQR in the sender and receiver Integration Engine in the corresponding system client.
Check the status of the scheduler and the status of the XBQ* and XBT* queues:
u25CF     Inbound qQueues
XBTI* (ExactlyOnce)
XBQI* (ExactlyOnceInOrder)
u25CF     Outbound queues
XBTO* (ExactlyOnce)
XBQO* (ExactlyOnceInOrder)
u25CF     Acknowledgment queues
XBTB* (ExactlyOnce)
XBQB* (ExactlyOnceInOrder)
u25CF     Large message queue
XBTL* (ExactlyOnce)
If the scheduler has the status Waiting, it is waiting for free work processes. This is why delays occur when XML messages are processed.
If not all necessary queues are registered, you can search for queues with the name prefix above using transaction SMQ2. Use transaction SXMB_ADM to register the queues in this case.

Similar Messages

  • Message Got Struck in Queue ----Repeatedly happening

    Hi Frnds,
    I am working on one scenarios File to IDOC, when i am sending messages to IDOC some messages got struck in Queue, when i am resending the messages manually  then its processing.
    why thi issues happends repeatedly, how to avoind this issue.
    Regards,
    Raj

    Hi
    Call the Integration Server and call transaction SMQR in the sender and receiver Integration Engine in the corresponding system client.
    Check the status of the scheduler and the status of the XBQ* and XBT* queues:
    u25CF     Inbound qQueues
    XBTI* (ExactlyOnce)
    XBQI* (ExactlyOnceInOrder)
    u25CF     Outbound queues
    XBTO* (ExactlyOnce)
    XBQO* (ExactlyOnceInOrder)
    u25CF     Acknowledgment queues
    XBTB* (ExactlyOnce)
    XBQB* (ExactlyOnceInOrder)
    u25CF     Large message queue
    XBTL* (ExactlyOnce)
    If the scheduler has the status Waiting, it is waiting for free work processes. This is why delays occur when XML messages are processed.
    If not all necessary queues are registered, you can search for queues with the name prefix above using transaction SMQ2. Use transaction SXMB_ADM to register the queues in this case.
    Check queue configuration
    For a complete analysis, make sure that the queues of the integration server are registered. To do this start the transaction for the Integration Engine administration (SXMB_ADM) and select the function manage queues.

  • Messages in "holding "status in Adapter engine

    Hi All
    We have a problem with the messages being stuck in " Holding " status
    We have resent the payloads for these messages,
    Although these messages have been manually processed,
    1) Messages went into holding status and are still remaining with the same status
    2) What we need to do to get rid of message ie. cancel, delete etc.
    Please dont send links, A solution will be appreciated
    Kindly help

    Rajeev
    I followed  this
    /people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework
    and the messages did get cleared
    However on the date it got  stuck to the Holding state
    it is still showing so .
    and am unable to get rid of  the same status for these messages for that date .. even tried a cache refresh but doesnt help
    kindly suggest
    /people/stefan.grube/blog/2006/04/27/how-to-deal-with-stuck-eoio-messages-in-the-xi-30-adapter-framework

  • When message got struck in XI

    Hi,
    Can anyone explain what and all steps we should perform when a message got
    struck in xi System ?
    Also where to find the log ,which gives clear information regarding message
    struck ?
    what is the difference between the logs in J2ee engine and that of in XI engine ?
    Please clarify my doubt
    Cheers
    Sanjeev.S

    Hi Sanjeev,
    when a msg is stuck in XI, then in SXMB_MONI, you can select the msg and restart it...........
    you can go to SXMB_ADM to register and activate your queues so that new coming msgs are not stuck in XI.........
    logs of J2EE engine show the startup and current status of your xi j2ee engine.....XI has both ABAP stack and JAVA stack...........so both engines have their own logs showing their status......
    Thanks,
    Rajeev Gupta

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

  • In Message Monitoring Message showing holding status

    Hi
    Can anyone solve this problem.Its urgent for me.
    My scenario is IDoc->XI->FILE
    The file i am trying to generate is an xml file which i am dropping in XI application server using File system.
    The problem is when i am going to see the message using transaction SXMB_MONI the perticular message interface is showing waiting for acknowladgement status .
    But in message monitoring in runtime workbench the it is showing following status:
    Adapter Engine
    <b>Holding</b>
    18.11.2005 05:42:09    
    CORP_SAP_DR2_030 http://limited.com/usa/sap_appl/retail/VendorsSAPAPOToMANU
    MIIA_Create  
    BS_MANU
    I am in SP14.
    Also the output xml file is not getting created in the XI application server.
    Please let me know the solution.
    Thanks
    Debraj Roy

    Hi Debraj
    HOLDING is a status which occurs normally for EOIO (Exactly Once In Order), so your message is set to Holding means some earlier message has not gone through. So until those messages are through this message will be in HOLDING state.
    Have a look at this link which explains how to handle such scenarios.
    http://help.sap.com/saphelp_nw04/helpdata/en/49/e3fb40ef74f823e10000000a155106/content.htm
    cheers
    Sameer
    Assign points if it helped you

  • 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

  • Messages in HOLDing status

    Hi Gurus,
    I have a problem with messages in XI. Some of them are in a HOLD status, some work fine. There is no reason why they should be in a HOLD status. I've checked SMQ1, SMQ2 - all clear.
    Is there I can do
    a, process these messages (they are now in AE waiting to be written in target file)
    b, to avoid this HOLD status in future
    Thank you,
    Olian

    Hi,
    In RWB -
    > Message Monitoring.
    Check the interface here and see what is the cause of HOLD.
    if you are using FCC in you CC then may be one/more fields having problem due to incorrect data.
    Also chekc RWB -
    > Component Monitoring (look at receiving CC)
    Regards,
    Sarvesh

  • PO Output message triggering even when it is on HOLD status

    Heelo SAP Gurus,
    I have come across a issue where the PO output message is triggering even when the user puts the PO on HOLD status.
    It is happening randomly i.e,not for all POs.
    Plesae guide me on this
    Santosh

    hi
    check your customizaton setting for the output type triggering event also settings

  • 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

  • Urgent - Messages in "HOLD" status - Alerting

    Is there any way that one can get alerted for messages being in HOLD status.
    say, for 2 hours.
    reg,

    Ahmad,
    If there is a message in HOLD status due to some reason, I want to get alerted and receive a message in the Alert Inbox.
    Please have a look at the note: 813993.
    PS: IF a EOIO message fails then the next one will be in HOLD state.

  • Messages in HOLDING status in AE

    Hi All,
    We have an issue with JDBC receiver EOIO messages, with messages going into HOLD status in AE , its a DEV environment :
    1) We have tried checking for failed messages before these messages we donot have any failed messages before these messages  just messages in HOLD..
    2) we are not able to delete or cancel these messages , we get a message cannot delete the message ,
    3) The message is doing a INSERT update to JDBC , JDBC connection is fine.

    Hi Kiran,
    Please let me know if your problem is fixed.
    I'm also facing the same problem in our Testing system where many messages are going to HOLD Status and also there are no messages in the System  Error state.
    We are trying to resend all the messages in every "Conversation ID". After this some messages gets successful and some will go into  Waiting status. We then cancel the messages in waiting status and resend all the messages in HOLD status and the process continues till all the messages in HOLD status in every Coversation ID were cleared.
    But this is a very very time consuming process.
    So can you please let me know if there is any solution for this prolem.
    Thanks,
    Pruthvi

  • How to STOP messages going into HOLD status very frequently

    I'm facing a problem in our Testing Environment where many messages are going to HOLD Status and also there are no messages in the System Error state.
    We are trying to resend all the messages in every "Conversation ID". After this some messages gets successful and some will go into Waiting status. We then cancel the messages in waiting status and resend all the messages in HOLD status and the process continues till all the messages in HOLD status in every Coversation ID were cleared.
    But this is a very very time consuming process.
    So can you please let me know if there is any solution to fix this prolem.
    Thanks,
    Pruthvi

    https://appleid.apple.com/cgi-bin/WebObjects/MyAppleId.woa/wa/directToSignIn?loc alang=en_US
    Go the the above
    Sign in. Go to the left side where it says phone numbers. Delete your number. Then save.
    Your iPhone friends will now get the red exclamation point that the message didn't deliver instead of it sending. Then your iPhone friend will force the message to go through as a text by long pressing the message and choosing send as text. Once tthey do that once you're set and all other messages will automatically send as texts for them to you. You just have to hope your iPhone friends realize to force the messages through as texts the first time around  but even if they don't at least they know they aren't reaching you and you aren't ignoring them.
    Does that help?

  • Alert for XI messages in a Holding status

    Is there a way to trigger an alert in XI 3.0 sp20 for messages that are in a holding status. Right now I am manually checking using the RWB but I would like to trigger an alert if messages are holding for an extended period of time. I have setup Email alerts for messages that have an error status but I can't seem to find out how to setup for messages that are holding.

    You can either configure CCMS alerts or using ALRTCATDEF. YOu can refer to the below links.
    CCMS:
    /people/aravindh.prasanna/blog/2005/12/23/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part--1
    /people/aravindh.prasanna/blog/2005/12/24/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-2
    /people/aravindh.prasanna/blog/2006/02/20/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-3
    Michal's blog-ALRTCATDEF:
    /people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
    Other help:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/80/942f3ffed33d67e10000000a114084/content.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/8fe69590-0201-0010-8097-c8a2ca60d5df
    Venkat.

  • Messages remain in Scheduled status in message monitoring in RWB

    Hi PI experts,
    I have got a situation where there are several messages showing in the Scheduled status. I followed the path RWB > Message Monitoring > Adapter Engine > Database (Overview) > Display.
    QoS for these messages is EOIO, however there are no messages stuck in the queue. All other channels are running smoothly. Only with this particular channel the messages remain in Scheduled status for a long time.
    I am neither able to make out the roor cause nor reprocess/resend these messages. Pleaes help.
    Regards,
    Dhawal

    Hi Suraj,
    What you said is absolutely correct. However, as I mentioned, the error message was not visible in RWB.
    My problem just got resolved. What I did is this,
    I followed the link http://<server>:<port>/MessagingSystem/monitor/monitor.jsp which is SAP Message Display Tool.
    Here in EOIO Sequence Monitor I found the error message and it's predecessor. When I resent the erroneous message from here, all subsequent Holding messages got processed.
    Thank you everyone for your help. Have a gr8 day...
    Best Regards,
    Dhawal

Maybe you are looking for