Inbound Queuing in SAP XI

Hello Friends,
                   please help me on the below issue. my error is when i am sending 1000 messages from jms to jms through  SAP XI all the
inbound queues are residing in smq2 . can i release all the queues at  a time once. please help me.

Hi!
As our SDN contributors already provided few links I  want t provide some information which is useful to you..
NOTE: Also please try to send one by one or atlease few messages other than sending 1000 at at time
I hope it will be useful to you in final case...because even I faced the same problem in BW- XI Integration but in those times I did the same... and also in final case if they restart the server once...all the messagse are gone I mean went to BW from XI by next day when I came there were no of messages
But before doing this please note these points:::
Even though you did this please make sure ...
1. Actually First check what is your Service Pack..as you told that it is XI check are you using SP22...in
    XI 3.0
2. Next check whether is it correct way to send 1000 messaegs at a time because may be your system  
    may be using some one and also if they are sending at the same time means...both of your queues wil
    be strucked..
3 First Go to SMQ1 (Outbound queue) and SMQ2 (Inbound Queue)and check how many messaegs are
   there See also make sure the status of those queues some may be SYS FAIL means system fail first
   delete those queues and then RESEND the remaining queues...
4.Also please go to RWB-->Communication monitoring and check your Communication Channel Status
    whether it was green or RED...and also check the AUDIT LOG..
5. Suppose if any errors are there or not even though once go to RWB--MEssage Monitoring and check on
    which basis and on which part it was strucked I mean whether the partiular message fails at Integration
    Engine level or else ADapter Engine level... and finally Check AUdit log...on due to which basis the
    messages are queues I mean due to huge size... of for what reason..
5.  Once do this if Still if you are facing same problem go to Transaction Code: SXI_CACHE and do cache
    refresh so that it may be reflected by refreshing all the IR and ID objects.
    Also do ADapter cache refresh...refresh in same Transaction code...
    Or else if you are adminstrator go to TCode : SMICM and go to MEnu--> As JAva and --> Do j2EE soft   
    Restart instead of Soft Restart...or else ask your basis poeple to do the same...
Note: WHile doing J2EE engine restart please make sure any Transactions or else any one or working on PI because it may take 20-25 mins to become server up again ...
NOTE: Also please try to send one by one or atlease few messages other than sending 1000 at at time
I hope it will be useful to you in final case...
I hope it will be useful to you in final case...Suppose if it is useful to you please close this and award points to the repective contributors if it is useful to you..
Regards:
Amar Srinivas ELi

Similar Messages

  • Inbound Queue blocked - SAP TM

    Hi guys,
    We are facing an issue regarding CIF. Seems like Inbound Queue in TM got blocked, original error was because number ranges for locations (what I think we already solved) but since queue is blocked we can not send fresh data.
    I've tried checking SMQ2 from TM side, and SMQ1 from ECC side, both are empty. Any idea how to unlock queue even if no records are displayed in SMQ1 (ECC) / SMQ2 (TM).
    Many thanks in advance!
    Martin,

    Hi Quanyin Su,
    Parallel and Alternative sequences are used in routing.
    I believe you are trying to CIF PPM/PDS from ECC to APO and you are getting this queue stuck at inbound of APO.
    Both the alternative and parallel sequences are supported in APO.
    Alternative sequence is used as alternative modes in APO.
    I can think of this as a master data issue.
    At least one of your work center used in either of the sequences is not available in APO or is not APO relevant.
    Could you please check your master data such as all the work centers used and make sure your parallel and alternative sequences are consistent.
    Once you made sure that master is available in ECC, you can CIF it to APO by using CURTO_CREATE transaction in ECC.
    Please see below link for Routing and its usage in APO:
    http://help.sap.com/saphelp_apo/helpdata/en/99/ed3a981d0f11d5b3fc0050dadf0791/content.htm
    You also need to activate a BADI in order to sent alternative sequences to APO.
    Below thread has all the details regarding this.
    Re: /SAPAPO/CURTO 103 : Mode .. is not assigned to an activity
    Regards,
    Abhay Kapase
    Edited by: AbhayKapase on Aug 5, 2011 2:24 PM

  • Mail to RFC -- Data Structed in Inbound Queue  -- Help needed !

    Hi Friends ,
                           I am doing Mail to RFC Asyn Scenario . Mail mails are come into the mail box . XI is trying to read the mail and send to R3.
                            It was working fine suddenly , Many mails read succesfully and data send to RFC , But it is structed in   ( SMQ2 ) inbound Queue ( <b>Message Scheduled on Outbound side</b> )
                  For long time it is showing like this . No data is accepted  by RFC. I have checked the Adpater confi for rfc it is fine .  I have given Max connection as 50 also .
              Please help me to solve this issue !
    Regards.,
    V.Rangarajan

    Hi,
    Have the Queues being registered in the R/3..?
    If not....
    1.Go to SXMB_ADM(R/3)
    2. Go to Manage Queues and then
    3. Register All Queues.
    <a href="/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically Failed Messages</a>
    Regards
    San
    <a href="Remember to set the thread to solved when you have received a solution to set the thread to solved when you have received a solution</a>
    Where There is a <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/weblogs?blog=/weblogs/topic/16">blog</a> there is a Way.

  • File to ABAP Proxy (problem with inbound queues in R3)

    Hi,
    In File-XI-ABAP proxy scenario, XI is successfully picking up file and sending it to R3.
    But in R3, an inbound queue is created in SMQ2 transaction code and I solved the same to automatically process the Queue by registering that in SMQR transaction code. But even though the inbound queue doesn't appear in SMQ2 (which means that it is processed successfully) it doesn't call the method EXECUTE_ASYNCHRONOUS. Can anyone help me whether I need to do any settings to run that method?
    Also can anyone help me, after the inbound queue is successfully processed in SMQ2 transaction, what would be the next step to watch what exactly that queue has done?

    Hi,
    Please check the program code for Server ABAP proxy.
    This will show you the trigerring of Proxy on inbound side.
    ABAP Proxy inbound program - sales order creation - Community Profiles - Wiki
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/abap%2bproxy%2binbound%2bprogram%2b-%2bsales%2border%2bcreation
    For Queues, you can go to SMQR and check for the register queue. Select and double click on it. If anything is stuck up then you can see in it. Even same with SMQ2
    Thanks
    swarup

  • Messages still stuck in the Inbound queue SMQ2

    Hello XI Gurus,
    All my messages with "READY" status are still stuck in the inbound queue (smq2) for the last 2 hours...there was no SYSFAIL error messages or scheduled background running. I have to manually go in and executed each of those messages, instead of automatically process it. Could someone please tell me how to troubleshoot this?
    Thanks so much in advanced,
    Dng

    Implement SAP note 758677 for this. This exactly deals with your issue.
    This Basically speaks about scheduling 'RSQIWKEX' for inbound and 'RSQOWKEX' for outbound queues.
    Also, you need to set the parameter 'QRFC_Restart_ALLOWED' to '1' in the transaction 'SXMB_ADM' -> Integration engine. Its in the runtime dropdown menu.
    Note : without this parameter being set this will not work.
    Thanks,
    Karthik
    Edited by: Karthik Rangaraju on Oct 1, 2008 2:13 PM

  • CREMDM splitted by PI, ADRMAS gets posted, CREMAS in inbound queue

    Hi all,
    I am on SAP MDM 7.1 SP03, SAP PI and SAP ECC6.
    I have gone thorugh all the threads and Guides related to MDM but couldn't find a valid solution for my problem described below. However, I did find some tricks and tweaking which I dont want to use as they are not recommended by SAP.
    We syndicated NEW Vendor records being created in MDM using CREMDM with standard Syndication Map. We have Vendors number generated in MDM and the number range being used exists in ECC and is marked as external. Moreover, the number range uses all of 10 digits, so there is no question of Conversion Routines with it. We deployed PI for splitting CREMDM to ADRMAS and CREMAS. We have serialized ADRMAS to go before CREMAS. We have assured that fields common between these two, have "no data" character i.e. "/" in CREMAS with correct data in ADRMAS. And ADDR_GROUP is mapped as "BP".
    Now the problem is, ADRMAS gets posted but CREMAS remains in the inbound queue. The queue running but still CREMAS remains there with CODE as "75". This results in non-creation od Vendor master record as CREMAS is not posted.
    Can anybody help with this. I really appreciate the support.

    Hi R,
    The ALE inbound function modules treat each IDoc segment as a current set of data. Missing fields (or fields that have no data) are interpreted as a value deletion. To keep the existing value for a single field, you have to add a no-data sign as field value for NAME_1. This no-data sign is a single slash (/).
    Please execute the inbound function module manually in WE19 to test this. If an exception is seen at NAME_1 ,pass a value or '/' and check for successful posting of Idoc.
    If this works, modify inputs to CREMAS accordingly.
    In addition a good SAP Note 1052964 - MDM: Distribution of Business Partners, Customers, Vendors for your reference.
    Regards,
    Vinay M.S

  • 545 mb file stuck in inbound queue

    Hi
    we are sending article master data from IS Retail to ftp server as flat file.
    data size is around 545 mb...it got stuck in inbound queue(smq2) ..
    error is : " Internally required memory is not available".
    XI server config : RAM - 16 gb.
    How to process such big file.
    what are the hardware configuration needed ?
    Regards
    Abhijit

    Hi Michal
    Thanks for your response
    This activity is done in PRD server.
    An idoc with 545 mb data is triggred from SAP.
    But it got stuck in inbound queue.
    I came across a thread ..
    Re: Processing large XML messages (>100Mb) in PI 7.1
    According to this thread we need to maintain a parameter
    icm/HTTP/max_request_size_KB  has default value of 102400 & maximum it can accept is 2097152
    Please suggest on this...do we need to maintain this parameter ?
    Regards
    Abhijit

  • Inbound queue error"XI Error APPLICATION_ERROR.ABAP: Queue stopped"

    Hi,
    In  SMQ2 ,we have received inbound queue error "XI Error APPLICATION_ERROR.ABAP: Queue stopped".When activate queue error is not going.So please advice.
    Thanks,
    Praveen

    Hello Mr,
    Have a look into SAP Notes: 824554, 906435, 783515, 910649, 706563.
    /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
    To be more helpful, can you post here complete error log?

  • Idocs in inbound queue

    Hi,
    We have a very critical issue wherein many a times in actual production system idocs are going into status 75 and hence into Inbound Queue.
    So user currently has to go transaction WEINBQUEUE and restart queue details.
    Just to give more technical details as only these type of idocs are going into queue's:
    Basic type: WMTOID02
    Message type :WMTORD
    Please help asap.Issue is very critical here.
    Thanks,
    Vikram

    Hi Ravi,
    Thanks for your quick response.
    As you have explained I see that from the Message Mapping I must mapping a timestamp in SERIAL field of the Control Record. This implies that the IDOC Receiver Communication Channel should not mark the checkbox "Queue Processing" (I get the feeling that this does nothing) and I have to mark the checkbox "Apply Control Record Values from Payload '.
    In conclusion, I understand that the IDOC Adapter for queued processing on a target system such as SAP adds nothing as standard. That is, I've mapping identifiers as timestamp to ensure the execution sequence in SAP and this will be done through a program in background. As is done with ALE...
    Furthermore, I can not avoid a "delay" in processing these messages. In my client does not allow me to schedule the job in less than 5 minutes.
    Is not there another solution where PI contribute just over? Any ideas?
    Thanks in advance,
    Jose.

  • XI inbound queues status "RETRY" in a new XI Production system

    Hi
    All the queues (XBT00* AND XBT02*) in XI Production system are not moving. Status is "Retry" all the time. The system is idle. Do you know what is happening here?
    I also see the following error in the queue:
    Command to tRFC/qRFC: Execute LUW again
    Also, lot of errors (below) in the system log (SM21):
    XIRWBUSER - Communication Error CPIC return code 027
    XIAPPLUSER - Perform rollback
    Any ideas?
    Regards
    Chandu

    Hi,
    When any message is sent from any other system to XI, the Inbound queue in XI is processed in the following way,
    1) AI_RUNTIME_JCOSERVER connects to the Java stack to execute the registered program AI_RUNTIME_<SID>.
    2) When this connection is fine, then the queue is processed without any issues.
    Now incase of Production system, which most likely to be a cluster system will fail because you'll find that AI_RUNTIME_JCOSERVER connection test fails, when you turn off one node. The reason being in visual administrator the JCo RFC Provider for the server nodes have not been maintained.
    Solution:
    Login to visual administrator, select the service JCo RFC Provider for both the nodes and set the value accordingly.
    Ex:
    SAP Cluster Virtual Name: XICLSTPROD
    Hostname1: XIPROD1
    Hostname2: XIPROD2
    SID: XIP
    CLIENT: 100
    Instance No: 02
    Values for Node1:
    Program Id: AI_RUNTIME_XIP
    Gateway host: XIPROD1
    Gateway service: sapgw02
    Server count: 20
    Application Server host: XICLSTPROD
    System number: 02
    Client: 100
    Language: EN
    User: PI_JCO_RFC
    Password: ***********
    Values for Node2:
    Program Id: AI_RUNTIME_XIP
    Gateway host: XIPROD2
    Gateway service: sapgw02
    Server count: 20
    Application Server host: XICLSTPROD
    System number: 02
    Client: 100
    Language: EN
    User: PI_JCO_RFC
    Password: ***********
    Change in the similar way for the other Programs registered.
    This should resovle the RETRY issue in Inbound queue.
    Hope this piece of information really helps.
    Regards,
    Kamesh

  • Error in inbound queue

    Hi,
    I have to monitor queues, when i use tcode smq2 for inbound queues, i see 4 queues with stuck messages. The status  is sysfail, so i do like this edit-> reset status ,then the status of the message has changed to transaction recorded. now i went to previous page and click unlock. when checked the first message status, it is XI  restart in qRFC not allowed.
    Suggest me where i went wrong and what to do to solve the issue.
    Thanks
    Jhansi

    Dear Jhansi,
    in his answer Chirag exactly describes how to proceed in this situation. For further information on how to process failed XI messages you might also have a look at OSS note 813029.
    Best Regards,
    Harald Keimer
    XI Development Support
    SAP AG, Walldorf

  • Inbound Queue Messages Idle

    Hi,
    We have seen several instances in our system where an inbound queue is in "Running" status and just hangs.  There is no SYSFAIL or any errors.  If we activate/unlock the queue, it restarts and processes as expected.
    I'm aware there are jobs that can be scheduled for those queues in error status, but is there anything that can be done to either reactivate or notify an admin when the queue is hanging/idle in the "running" status automatically?
    Any help would be greatly appreciated.
    Thanks in advance.
    Best Regards,
    Duke

    Hi, Duke.
    Regarding notification, CCMS might be useful.
    http://help.sap.com/saphelp_nw04/helpdata/en/8b/ceea3b31aac554e10000000a114084/content.htm
    Running status can be also checked as "blocking".
    Hope this helps.

  • Parking error msgs from Inbound queue

    Hi Experts,
    There are situations when an inbound queue (SMQ2) gets build up because of an error msg. In this case, we manually cancel the error msg and allow subsequent msgs to get process. Is there any way using which we can park the error msg aside automatically (into some new queue, like an error queue) and allow subsequent msgs to get process. This will prevent queues from building up and we can fix all the error msgs at later point of time by checking them from newly created error queue.
    Thanks,
    Aditya

    Hi,
    PI 7.3 has the feature of parking the error queues aside and allows the other messages of queue to process....
    I heard this feature is downported to the PI 7.1 also...but no hands on or more info at hand on this...if your are using 7.1 check the sap site...
    Apart from that try to check for activation of CCMS alerts so that person is notified in case if message in queue gets blocked..
    HTH
    Rajesh

  • Inbound queue in APO side

    hi,
    All R/3 changes are not transfered to APO. It got stuck in SMQ2 in APO side. every time i am manually activating  those queues in ready status.
    1) Is there  any simple way to activate all the queues having status "ready" in single execution.
    2) what will be the reason for inbound queue and how to avoid? i able to see only "ready" and "waiting" status queues there is no error

    Hi,
    Please check the status of the QIN and QOUT scheduler in transaction SMQR/SMQS and see if the destination is registered or not. I am pasting the content of the SAP Help for you quick reference.
    Set Up QOUT Scheduler
    Use
    Queued Remote Function Calls (qRFCs) are used to transfer data between SAP APO and SAP R/3. The QOUT scheduler processes outbound qRFCs (outbound queue).
    You complete the following steps in the relevant client in the production system.
    You call the QOUT scheduler using transaction SMQS. The destinations to which the outbound qRFCs are to be sent are registered in the QOUT scheduler. As of version 6.20.45 this is done automatically.
    The following options exist for a registered destination:
    Type
    R: The destination is registered, that is, it is started using the QOUT scheduler.
    U: The destination is not registered, that is, it is not processed.
    N: The destination is not processed using the QOUT scheduler, but is sent at the time of the COMMIT WORK.
    Max. Connections: Number of connections that are used to send the qRFCs. The default value is 10 for R/3 connections and 1 for TCP/IP connections.
    Max. Runtime: Time that a destination is processed by the QOUT scheduler. The default value is 60 seconds.
    The destination NONE means that the qRFCs are processed in the local system and should not be registered up to version 6.20.45, supplement 8 inclusive. As of supplement 9, NONE can be registered and the without tRFC option set.
    Requirements
    The qRFC configuration must be configured. For more information, see
    Set Up QOUT Scheduler
    Use
    Queued Remote Function Calls (qRFCs) are used to transfer data between SAP APO and SAP R/3. The QOUT scheduler processes outbound qRFCs (outbound queue).
    You complete the following steps in the relevant client in the production system.
    You call the QOUT scheduler using transaction SMQS. The destinations to which the outbound qRFCs are to be sent are registered in the QOUT scheduler. As of version 6.20.45 this is done automatically.
    The following options exist for a registered destination:
    Type
    R: The destination is registered, that is, it is started using the QOUT scheduler.
    U: The destination is not registered, that is, it is not processed.
    N: The destination is not processed using the QOUT scheduler, but is sent at the time of the COMMIT WORK.
    Max. Connections: Number of connections that are used to send the qRFCs. The default value is 10 for R/3 connections and 1 for TCP/IP connections.
    Max. Runtime: Time that a destination is processed by the QOUT scheduler. The default value is 60 seconds.
    The destination NONE means that the qRFCs are processed in the local system and should not be registered up to version 6.20.45, supplement 8 inclusive. As of supplement 9, NONE can be registered and the without tRFC option set.
    Requirements
    The qRFC configuration must be configured. For more information, see
    Regards,
    Senthilrajan
    Edited by: Senthil_APO on Oct 12, 2009 10:54 AM
    Edited by: Senthil_APO on Oct 12, 2009 10:55 AM

  • Problem Inbound Queue SMQR after execute BUPA_DEL

    Good Day
    Now, we developing a interface for a customer to import Business Partner (BP) from a non-SAP System in our SAP CRM 2007 System. To validate the functionality of the interface we would like to make any test imports. Well, if we finished an import we have to delete the BP's with the transaction BUPA_DEL. The deletion of the BP's in the table BUT000 seems to be ok.
    So, when I call the transaction smqr to check the Inbound Queue CSA*, I will found an entry with the state "Retry" for every deleted dataset. I can manually execute the Queue successfully. What could be the reason for this state? How can I automate the execution of these queues?
    Many thanks for your support!
    Regards
    Marco

    Dear Gerhard
    Thank you for your answer.
    Well, I had already implement the solution of the note 785046 without success.
    The clue is, no Background-Job is scheduled but there are many thousend Entry's with the state RETRY in the Queue...
    In the SysLog I couldn't found any messages they indicate to this "problem".
    Do you have any idea's.
    Can I manually schedule a Job (may be periodically) to process these Queues?
    Thank's for your replies!
    Best regards,
    Marco

Maybe you are looking for