Sysfail locks smq2 queue

Hi,
We are live with our PI7.1 system as of 11/6 and are seeing serious issues when a data error causes a sysfail for a SMQ2 queue.  At this point the queue is locked for further processing.  We have monitors setup which page us for this situation.  However, we really need to prevent the queue from locking so other messages are sent even when one item is in sysfail status.
Notes 813209 and 1118297 do not seem to offer any help is this situation.
Is there a way to prevent the queue from locking due to sysfail status messages?
Any help is greatly appreciated.
Regards,
Rick Taylor

Rick,
Check out this blog..
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417500)ID1371322850DB11715461650132929943End?blog=/pub/wlg/2728
"For automatic qRfc failure recovery, schedule the report RSQIWKEX to run periodically. This report enables automatically resets the queues. "
I remember there is a way to put error messages in different queue so that current queue wont b lock anymore...I'll check and let you know.
Hope this will help.
Thanks,
Nilesh

Similar Messages

  • Running smq2 queues in debug mode

    Hi,
    Can anyone tell me how to successfully run an inbound queue in debug mode.
    Following are the steps undertaken.
    I locked the queue in SMQ1. The Queue is set to STOP state.
    I then triggered an sBdoc flow into CRM.
    I am expecting the sBdoc to be in an intermediate state, but to my surprise it is coming as Fully Processed.
    At this point, setting Debug mode in smq2 and Unlocking the queue does not help me analyse the bdoc/process flow as the bdoc is allready processed.
    Any inputs in this regard would be helpful.
    Thanks & Regards
    Ron.

    Hi Ron,
    Please check below blog, hope it helps u.
    Regards,
    Deven
    /people/lokesh.aggarwal/blog/2008/02/27/debugging-crm-middleware--sales-document

  • SMQ2 queue is blocked and messages are in u201Cwaitingu201D status in RWB

    Hello,
    A SMQ2 queue is blocked with XXX data and these messages are in u201Cwaitingu201D state in RWB. 
    What could be the reason?
    Im sure its not because of the space because all the messages which flow after that was there in the directory.
    Regards,
    Mathangi

    Hi Mathangi,
         double click on the queue and click on the first message which will direct to MONI
    --> check what exactly the error is and try to resolve the error accordingly
    if you are unable to do that
    Right click on the first message and save LUV it will be saved in SMQ3
    then unlock the queue and execute again it will process successfully..
    later you can process the message which is saved
    Regards,
    Naveen

  • SMQ2 queue deletion.

    Hello Everyone,
    Is there a way to delete the SMQ2 queues in SRM? We have thousands of records and we do not want to delete each queue manually.
    Any help to get this?
    Regards,
    Khushbu.

    Hi Kushubhu
    See  the following link it may be helpful for you.
    Re: Mass Delete of BDocs in SAP CRM system
    with regards
    Manjunath

  • SMQ2 Queue sys.failed

    HI all,
    In CRM system SMQ2 queue name  R3AD_ACCOUNTING is getting system failed.
    When iam trying to unlock,activate and Execute those queue entries(5677) its not working i am getting the Message that FUNCTIONAL MODULE DOES NOT EXIT  for this iam deleting the queue entries one by one after checking each one.
    This queues are coming from R3 because of sale/service billing document post. when i check in SMW01 i didnt get any information related to this queue.
    Is it any other way to solve this issue. How to resolve ?
    Do the needful..
    regards,
    shoki.

    HI,
    when i check the queue entries i got the Functional module BAPI_CRM_SAVE,and queue name R3AD_ACCOUNTING, STATUS TEXT says that " Bdoc status failed,Bdoc not found".
    system doesn't have dump errors too.
    I came to know that when ever you get the message "Function module not found for this exception" for Queue entries we can delete that queue entry, but  the problem is i have so many entries, Its not possible check one by one and delete?
    sould i delete this all entries at once? Is it any solution?
    Thanks,
    shoki

  • Locking a Queue.

    I am doing a program in which there are 2 threads - first thread will add integer values to a queue and the second thread polls the value from the queue. I need to lock the queue so that both add and poll wont happen simultaneously. How can I achieve this? How can I lock the queue? As I am newbie to concurrency, somebody help me with code snippet. Thanks in advance.

    sowndar wrote:
    As I am newbie to concurrency, somebody help me with code snippet. Thanks in advance.You cannot code snippet a complicated concept such as this. There is only one way to go: learn this stuff, learn it well and design your code to be concurrent from the beginning - you won't get it done by plugging in two lines of code, I can tell you that.

  • Is commit lock on Queue or QueueSpace?

    Hello,
    when a transaction is committed in a Tuxedo Queue (/Q), does that lock the
    queue only or does it look the whole queue-space?
    I have a /Q with multiple TMQFORWARD and service handlers. There is a
    backlog in the /Q, but occasionally I have observed that no messages are
    being processed for a few seconds.
    I measure in the service handler the time between the tpreturn() and the
    next invocation. The TMQFORWARD idle time is 1 second.
    So, with lots of messages in the queue I would not expect to see more than
    one second between requests. But I see 2 - 3 seconds occasionally.
    My conclusion is that one TMQFORWARD takes some time to commit (the
    transaction also include Oracle via XA). It is quite reasonable to assume
    that during the commit, no other TMQFORWARD can manipulate the queue.
    My next thought was to have multiple queues (in the same queue space). But
    if the commit locks the queue space, then this will not help.
    Thanks...
    Roger

    Roger,
    /Q uses several types of locks, including a lock on the entire queue space,
    locks on individual queues, a lock on the transaction table, and locks on
    several other tables. The lock on the entire queue space is used only when
    creating, opening, or destroying a queue, and is not used when committing a
    transaction. However, committing a transaction does require a lock on the
    transaction table for short periods of time, and the transaction table is
    shared between all queues in a queue space. Therefore, there may be some
    degradation in commit performance caused by combining multiple queues in one
    queue space, but it should not be much. Combining multiple queues in one
    queuespace rather than multiple queuespaces also has advantages, including
    the ability to allocated shared memory and disk resources as best benefits
    all of the queues rather than deciding on a fixed allocation at the time the
    queuespaces are created. Depending on the particular application and how it
    is configured, this resource sharing benefit might or might not outweigh the
    overhead of a transaction table lock shared between mulitple queues.
    Queuespaces are often large, and involve many I/O operations (except for
    in-memory queues.) The allocation of queues and queuespaces among different
    disks can improve performance if an application is I/O bound. Different
    queuespaces will necessarily reside on different filesystem paths, which may
    be located on the same or different physical disks. A single queuespace can
    reside on a single filesystem pathname, but can also reside on multiple
    filesystem pathnames by using the qmadmin "qaddext" command if this is
    judged to be desirable.
    "Roger Fischer" <[email protected]> wrote in message
    news:[email protected]...
    Hello,
    when a transaction is committed in a Tuxedo Queue (/Q), does that lock the
    queue only or does it look the whole queue-space?
    I have a /Q with multiple TMQFORWARD and service handlers. There is a
    backlog in the /Q, but occasionally I have observed that no messages are
    being processed for a few seconds.
    I measure in the service handler the time between the tpreturn() and the
    next invocation. The TMQFORWARD idle time is 1 second.
    So, with lots of messages in the queue I would not expect to see more than
    one second between requests. But I see 2 - 3 seconds occasionally.
    My conclusion is that one TMQFORWARD takes some time to commit (the
    transaction also include Oracle via XA). It is quite reasonable to assume
    that during the commit, no other TMQFORWARD can manipulate the queue.
    My next thought was to have multiple queues (in the same queue space). But
    if the commit locks the queue space, then this will not help.
    Thanks...
    Roger

  • Why orders gets locked in Queue's

    Dear all,
    Could you please help me to know why orders gets locked on Queue's as well SMCL trasaction.
    what is the route cause for that? and is there any why we can unlcok automatically with a program?
    please suggest me.
    Thanks for your help.
    Regards,
    Shaik

    Hi Shaik,
    Orders you are seeing in SMCL transaction is Cross System Locks. When Scenario A is activated, then Cross System Locks must be activated.  This locks will be released automatically from the system when the transaction is completed successfully in ECC & CRM.
      You are not supposed to remove the locks for the orders from SMCL transaction directly. First analyze the issue with the order. If any issue in order replication from CRM to ECC or vice versa Cross system lock will not release automatically.
         For example, from SMCL take one order and analyze the order in ECC & CRM, definately you should see the difference in ECC and CRM order.
      Some times Cross System Locks will not be released, if updates are not coming to CRM from ECC, better check filters in SALESDOCUMENT middleware object for the sales document types.
    Regards,
    Bhanu

  • SYSFAIL in SMQ2 in Device Reassignment Queues

    Dear SUP developers,
    Device Reassignment Queues(Pattern: DOE_Q_*) got failed in SMQ2 with error
    "Exception occurred due to http communication failure"
    in Function module "SDOE_ESDMA_EXECUTEQOS".
    I didn't find any related dump in ST22.
    Please help me to resolve the issue.
    lakshman balanagu.

    SUP server is not reachable from DOE.
    Please check following things.
    1. Check whether address provided while deployment of the bundle in SUP is correct or not? The information will be in sup-db.xml file.
    2. If yes, Then check whether IP is reachable or not?
    3. If yes, check whether port provided is reachable or not?
    Regards,
    Siva.

  • SMQ2 Queue Monitering and stuck up problem

    Hello Experts ,
    Below is the situation
    u2022     An interface is asynchronous In bound in ECC from PI as a PROXY message and the quality of message is EOIO (Exactly once in order) i.e. it has a definite queue.
    u2022     The actual method of the Provider class has the code which posts the data into the ECC system using BAPI.
    u2022     If BAPI is successful the message is successfully passed BUT if BAPI returns an Error an exception is raised (CX_AI_APPLICATION_FAULT) and the errors are logged into Zee tables. After the resolution of errors the xml id is reprocessed using SXI_MONITOR  Tcode
    Concerns
    u2022     As the Message quality type is EOIO  it has a dedicated queue and if the first message in the queue fails  the queue is  in status  SYSFAIL  , as per in tcode SMQ2
    u2022     The status text for the ID in the Queue is - An exception occurred that was not caught.
    u2022     Due to this all the rest of the messages in the queue get stuck up i.e. Scheduled state, unless and until you go to SMQ2 and delete the message with the exception.
    u2022     Expected is that the queue should not stop or not go into SYSFAILT if an application exception is thrown.
    u2022     In our situation the message volume in the queue is LARGE may be 5K message a day.

    Anup Deshmukh wrote:
    Hello Experts ,
    > Below is the situation
    > u2022     An interface is asynchronous In bound in ECC from PI as a PROXY message and the quality of message is EOIO (Exactly once in order) i.e. it has a definite queue.
    > u2022     The actual method of the Provider class has the code which posts the data into the ECC system using BAPI.
    > u2022     If BAPI is successful the message is successfully passed BUT if BAPI returns an Error an exception is raised (CX_AI_APPLICATION_FAULT) and the errors are logged into Zee tables. After the resolution of errors the xml id is reprocessed using SXI_MONITOR  Tcode
    > Concerns
    > u2022     As the Message quality type is EOIO  it has a dedicated queue and if the first message in the queue fails  the queue is  in status  SYSFAIL  , as per in tcode SMQ2
    > u2022     The status text for the ID in the Queue is - An exception occurred that was not caught.
    > u2022     Due to this all the rest of the messages in the queue get stuck up i.e. Scheduled state, unless and until you go to SMQ2 and delete the message with the exception.
    > u2022     Expected is that the queue should not stop or not go into SYSFAILT if an application exception is thrown.
    > u2022     In our situation the message volume in the queue is LARGE may be 5K message a day.
    Why dont you have Fault message mapping , that captures the exception and trigger an alert using the alert framework..
    Best Regards,
    XA

  • How to debug XI--- R/3 (abap server proxy) code,  SYSFAIL in SMQ2

    Hi
    i have a XI (BPM) to R/3 (ABAP server proxy) scenario,
    when the data goes from XI to R/3, it is getting stuck at R/3 inbound queue (SMQ2), with status : SYSFAIL and error text: "No roll storage space of length
    3391496 available for internal storage",
    we tried activating the queue/ reexecute the LUW, but it still shows the same error status after running for some time,
    how can i debug the ABAP server proxy,
    pls tell me how can i debug the ABAP proxy code in the R/3
    very critical issue

    Have a look at SAP Note 17965 - No storage space available
    Regards,
    Prateek

  • SMQ2 Queues Stuck

    Hello All,
    I have a problem of one of the queues in CRM 5.0 is struck with SYSFAIL error. The queue name is R3AD_MATERIAFAYB401007. When I double click the queue entry I get the error on FM  BAPI_CRM_SAVE with the remote user of R/3. The statustext is is 'Error in Mapping (Details: transaction SMW01)'.
    Does any one knows how to set this queue right ?
    Regards
    Rashit

    Rashit,
    You probably are missing product categories in CRM.
    Follow this process,
    1. Run initial load transaction R3AS for object 'DNL_CUST_PROD1'. Make sure source is 'OLTP' and destination is 'CRM'
    2. Monitor the request load using transaction R3AM1 and make sure it completes
    3. Go to SMQ2 and double click on the Queue in SYSFAIL status. Select the Queue and click on 'Edit' and click on 'Reset Status'.
    4. The Queue should start Running and material should be updated in CRM
    <b>Please award points if it helps.</b>
    Regards
    Haseeb

  • SMQ1 and SMQ2 queues stuck

    Hi All,
    We are using ISU and CRM system for Retail business, Always work flows and lot of business transactions will perform in those systems and replications will happen in both systems.
    Due to this reason lot of entries are present in SMQ1, SMQ2 and SM58 will present. We are continuously monitoring though some times some entries are are found in sysfail status. due to this lot of entries are piled up and queues becomes very high amount.
    As a work around, If we unlock the queue ( sysfail entry ) two to three times the entry will go and the remaining entries will start move.
    Currently our requirement is can we do this kind of this as automated ? I mean as per conditions it will unlock the queues automatically ?
    Please suggest me in this case.
    Thanks in advance.
    Pavan.

    Hi Dustin,
    Thanks for your reply. I had gone through the mentioned notes and say about it is not recommended to use regular basis. Here our requirement is need to check the sysfail entries in the queue. Need to unlock the queue twice or thrice to re-process the entry. If any data issue our CRM middle ware team can handle.
    The major purpose is to unlock the queue entries which can re-process automatically without manual correction.
    I like to proceed with Deepanshu suggestion to check with ABAPer. before that I need to check with our CRM middle ware team to get the list of error which can process through unlocking the queue.
    Will keep you posted the updates. Thanks a lot for your time and response.
    Thanks,
    Pavan.

  • TimeOut Exceeded in SMQ2- queue Block

    Hi all,
       I am having an issue with my production  PI BOX. Not sure if there is any solution for this.
    I have some interfaces in PI which expects huge payload data.Sometime the messages are getting failed in SMQ2 with error message " Time Limit Exceeded ". This is not happening with one particular interface message.Sometime teh queue got blocked for one interface and then the other day with some other interface.
    When i tried to resend the same messages by selecting Execute LUW option, all of them have gone through fine. But we cannot do this manually everyday. I just wants to know where exactly the time out parameter has been maintained for pipeline processing.
    The messages are getting timed out in receiver grouping pipeline step.
    I have gone through the =  Michal Blog : 3802 about the time out. But nothing helpful on that.
    Could anyone of you help me out here?

    Hi
      We are using JDBC communication channels for all these interfaces. But messages are failing in SXMB_MONI .ideally it means that messages are still in Integration engine. right?
    It doesn't send teh message to adapter engine
    If we increase timeout level  at adapter level, does it really help? If yes how come? Could you please explian?
    Thanks
    Rajesh

  • SMQ2 queue stops

    Hi,
    I have an integration process that sends a synchronous message (soap adapter) to a receiver system.  After that  the receiver system needs about 5 to 10 minutes to respond to the request. Sometimes this is no problem and the queue of outgoing messages resides in status running.
    However most time the queue stops after some minutes and the only way to go on with processing is to manually unlock the queue in SMQ2.
    Why does this happens? Is there a possibility to restart the queue automatically? Is there a timeout period in queue processing that can be inceased?
    Thank you in advance,
    Daniel

    Dear Daniel,
    In synchronous scenarios running over PI, several communication components are involved where each may lead to a time-out. Such a time-out on one communication component causes the messaging scenario to fail as a whole.
    Various components which may contribut for your queue to fail are:
    Messaging System specific time out, SOAP sender channel time out, and your receiver Adapter time out property.
    There are some pre defined values for them already set in our PI system and these needs to be changed to accomodate the failure case also.
    To give you a lead, In NWA, Go to->Operation Management->Systems-> Start & Stop -> Java Services -> (Under Related Tasks) Java System Properties. Select your adapter type and under properties change the default time.
    For Sender SOAP channel, add u2018Parameter Nameu2019 as: XI.Timeout and in u2018Parameter Valueu2019, give any value in milliseconds.
    Warm Regards,
    Anshul

Maybe you are looking for