Inbound Queue Stuck

Hi,
We send about 7000 IDOCs to PI. These IDOCs are sent to the PE for a ccBPM.
However, the Inbound Queue got stuck with status of the first message on "Transaction Executing". This stayed this way for 2 days.
In the end we locked and unloced the queue and every thing was running again.
But a few minutes later all the data was punt into the BPM queue and nothing was happing. (first record had status "transaction recorded"). I had to activate the QIN scheduler and everyting was running again.
This is happening in a production environment and is not acceptable (processes run at night).
Does somebody have hints where to start looking or have a solution?
Ron

Check this blog :
XI : How to Re-Process failed XI Messages Automatically
Note 527481 - tRFC or qRFC calls are not processed
Regards
Gangaprasad

Similar Messages

Inbound Queues stuck with RFC errors

Hi Experts,
Greetings for the Day !
We have BDOC related issue and we need your expert help ASAP in resolving the same.
We ahev a few BDOCS lying in intermediate state in transaction SMW01, which we found using BDOC monitoring on daily basis. When we check the same in SMQR - inbound queue, we found that the queues are stuck with an RFC error message.
We are re-activate these queues to actually resolve the intermediate bdocs. But, my query is
1> The raeson for getting these BDOCS in intermediate state & stuck queues
2> A permanent resolution for the same.
Please help and let us know if you need more details.
Regards,
Kanika

Hi Kanika,
RFC error can be due to a bad connection as well. If the server is down, there might be a problem in communication with the connected system and the queues will not be processed further. You need to reactivate or unlock to get the queues processed.
But if there are any specific errors for which the queues are stuck do state the same, so that we can look into an actual resolution.
Regards,
Venkat

CRM Inbound Queue Stuck

Folks,
The status of my inbound queues in CRM is "stop". Tried activating it, unlocking it but it does not seem to work. This is a newly configure box where I just got done making related queue entries in smqr and trying to download a object in R/3. The object is in "running" status. Any idea what I am missing ?
Faz

Hi Fasi Syed.
How about the results of the Tx MW_CHECK or the SMWP. Usually you get some info there to start your analysis.
Regards
Thomas

Messages stuck in SMQ2 Inbound Queue.

Scenario: File->XI->Proxy
When I put 50 files at the same time in a directory, channel is configured Exactly Once in Order and we have created queue with the name GATQUEUE. The messages are picked up from directory and sent one by one to BPM process. 31 messages out of 50 poccesed succesfully but 19 of them get stuck in the queue always. Though GATQUEUE is released lately but they are stuck in 'XBQO$PE_WS90000013' queue. This is seen in SMQ2 Inbound Queue.
Could you please tell me how to release this message which are already stuck and what bit of configuration required so that it works for 1000s of files/messages at a time?
Thanks
K

Hi Kiran,
Just add the below parameter in XI tcode : SXMB_ADM
Execure Integration Engine and Configuration.
Click on Specific Configuration, go to change mode
Click on New entries
Category : MONITOR
Parameter :QRFC_RESTART_ALLOWED
Current Value : 1
Save.
Regards,
Venu.

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

Messages stuck in Inbound Queue with Ready Status

Hi All,
The messages in the Inbound queue are getting stuck in Ready status.
I have to manually Unlock each queue to start the processing.
After some time again all the message queue are back to the Ready State.
Please help me on this issue.
Regards
Milan

go to --> sxmb_adm
Manage Queue
Select all Queues, Activate Queues.
& check your scenarios, now it will not stuck due to this error.

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

Msgs getting stucked in inbound queue

Hi All,
I am doing a jdbc- xi - ABAP proxy scenario. Data is coming into the R/3 via proxy but getting stucked up in inbound queue. When I go to the queue I can find entries with msg transaction recorded. When I manually execute the entry from the queue it is getting executed successfully.
In R/3 the msgs are with a green flag(scheduled). But when i execute it from inside the queue, I can see the success flag(chequered) one.
Why am I getting this problem?
Kindly help me debug this issue.
Thanks & Regards,
Jai Shankar.
Message was edited by: Jai Shankar

Hi,
Pls make sure your queues are registered and active...
you can register the queues using the SXMB_ADM transaction and executing the link "Manage Queues" in that.
Thanks,
Renjith

Inbound Queues getting stuck up in PI7.1 for Idoc scenario Mpackg. enabled

Hi Experts,
We have an issue while processing Single Idocs in PI 7.1.
we have extended MATMAS05 and we are processing these via PI to FTP folder.
The inbound queues are frequently getting stuck.we will be sending atleast 1000 idocs every hour from R3.The processing time is very slow for this interface and its impacting other interfaces which we are currenlty having.
We have followed the webblog by William Li "Step-by-Step Guide in Processing High-Volume Messages Using PI 7.1's Message Packaging" but still the processing time for Single Idocs is very slow.
We have to use single idocs as we will send only the changed materials from R3.
Could you please assist us in overcoming this issue.
Many thanks in advance.
Points will be awarded for valuable feedback.
Cheers
Jyoti

Hi Jyoti,
Message Packaging works PI7.0 SP 13 and PI7.1 .
we have to configure Message Packaging manually ,
Step 1) 1. Enable packaging for the integration server
SXMB_ADM -> Change Configuration (F9), create a new entry:
Category: RUNTIME (PI7.1)
Parameters: PACKAGING Current Value: 1 (for active) .
Default Value in PI7.0
Current Value: 0 (for inactive)
Step 2) Create "Package Configuration Type u201C
Use Transaction SXMS_BCM .
Configuration Type : Any name.
Description: any text to describe the configuration type .
Wait Time : 60 seconds
Number: 100
Maximum Package Size. 2 MB
Step 3) Create "Sender/Receiver Definition
Transaction :   SXMSIF (Create New Entry).
Sender/Receiver ID:PACKAGE_DEMO .
Description :
Interface Name: Interface Name used in Receiver Determination.
Interface Namespace:   Interface Namespace used in the Receiver Determination .
Step 4: Create "Specific Package Configuration"
Transaction :    SXMS_BCONF .
Step 5: Package Monitoring
TX: XMSPKSTATCNF
Follow above steps and configire message packaging , then you feel diference,
actuualy i configured message mackaging,i am feeling the difference.
if any issues let me know.
Cheers,
Raj

Message stuck in inbound queue of r/3 for inbound proxy

Hi Experts,
The scenerio is Inbound Proxy.
I m using standard prgram rfbibl00 to post a document (FB01) in Inbound proxy. When the message is triggered from XI, it get stuck in inbound queue of R/3 ( SMQ2) giving the status text "Session 1: Special character for 'empty field' .
Please help to resolve this issue.
Thanks in advance.

dear experts,
did u get chance to look into this issue.
Thanks in advance.

Screen output without connection to user, Message struck at inbound queue

Chaps,
I executed inbound proxy form PI 7.0, the message was struck in the inbound queue of ECC 6.0,
with status text "Screen output without connection to user" then when I apply execute LUW then it is converted to
"ThiSend:bad tm type /connection closed (no data)".
when i test the same message from 'SPROXY' t.code, inbound proxy class was working fine.
I came to know that when we call an ABAP program in side a proxy then it will throw same error what I got by checking the below url
Message struck at inbound que in server proxy
But in my proxy. I am just putting the data into z table and on some condition I am calling some other BAPI call.
Here my doubt is calling the SUBMIT for other ABAP program is same as calling the BAPI call?
because in the above thread clearly saying that don't use the other ABAP program in proxies. is the same case for calling the BAPI call into the proxy?
In proxy, the logic is I am just simply reading the data from IS(integration server, PI7.0 SP 18) to ECC 6.0(SP14) if the row is not there the data is reading into table. If row is already there then it is stuck up in SMQ2 (inbound queue) of the ECC
am I missing any basic things? please guide.

But in my proxy. I am just putting the data into z table and on some condition I am calling some other BAPI call.
Here my doubt is calling the SUBMIT for other ABAP program is same as calling the BAPI call?
I too believe ..
because in the above thread clearly saying that don't use the other ABAP program in proxies. is the same case for calling the BAPI call into the proxy?
It is saying not suggestable...!!!! BAPI calls work perfectly !1
In proxy, the logic is I am just simply reading the data from IS(integration server, PI7.0 SP 18) to ECC 6.0(SP14) if the row is not there the data is reading into table. If row is already there then it is stuck up in SMQ2 (inbound queue) of the ECC
am I missing any basic things? please guide.
Seems so,
Lets try below things..
1. Plz check the user is having auth to run the executable program in ECC.
2. It seems that you are not using the proxy structures in a correct way..and check the calling program also..!!
Edited by: Santosh Rawat on Jul 30, 2009 1:12 PM

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

R/3-- XI, queue stuck problem, concept not clear

Hi Forum,
I have a R/3(abap proxy)----->XI scenario,
now the data being sent from R/3 to XI is getting stuck (due to some HTTP error) in the queue, which is visibale through tcode SMq2 of R/3,
I want to know, why the stuck queue and hence the LUW is seen through SMQ2 (inbound queue), and not SMQ1 (outbound ) queue,
though i m under an impression that outgoing messages uses outbound queues,
pls clarify this concept

Go to SMGW -> Go to -> Logged on Clients, check your Program ID is registered there or not ?
Did you follow Michal's blog
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
Bean not found error is due to incorrect configuration of RFC Dest, but per your initial message it does not look like, but worth following Michal's blog.

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

Inbound Queue Stuck

Similar Messages

Maybe you are looking for