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.

Similar Messages

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

Automatically restart messages stuck in smq2

Hi,
I am having a problem that messages are getting stuck in the inbound queue and I need to manually restart it.
I have searched on this and have found that RSQIWKEX job can be used for this. I have tried testing it but the messages are still stuck in queue. It is having the status as SYSFAIL. Is it not possible to restart messages having this status?
The error which is there for SYSFAIL is Time Limit exceeded.
Please help me to restart such messages automatically which I am now doing manually.
Thanks and regards,
Siji Anup

Hi ,
Pasting below the content of st22
The program "CL_XMS_PERSIST================CP" has exceeded the maximum
permitted uninterrrupted
runtime and has therefore been terminated.
The system profile contains the maximum runtime of a program.
When this time limit has been exceeded, the program is terminated
to make way for other users who may be waiting.
In the case of a work area, this means that
- endless loops (DO, WHILE, ...),
- database accesses producing an excessively large result set,
- database accesses without a suitable index (full table scan)
do not block the processing for too long.
The maximum runtime of a program is limited by the system profile
parameter "rdisp/max_wprun_time". The current setting is 1800 seconds. After
this limit has
been exceeded an attempt is made to interrupt the SQL statement running
or to tell the ABAP processor to interrupt the current program. A
maximum of 60 seconds is then waited. If after this time the program is
still active then the work process is restarted.
Thanks and regards,
Siji

Messages stucked in moni with queue status as "RUNNING"

Hi All,
Few of messages stucked in moni with queue status as "RUNNING" from the past 6 to 7 hours. all the stucked messages running on same dialog instance app server 03 (ucobpi03_PIP_03). i checked PIP appserver its working fine.
Can any one please expalin me how to clean the queues..is there any effect of other queues ?
Thanks,
Siva.

Hi,
it can be due to multiple reasons....
check the interface logic built ...it can be either due to this or can be of large volume of data...
Also check the queues have been registered or not...
HTH
Rajesh

MEssages Stuck in SMQ2 - Automation of moving error msgs

Hi ,
We face a lot of issues with messages getting stuck in SMQ2 and blocking all other messages.
Right now we Save the LUW and move it to SMQ3
but is there an automated way/ configuration to move the errore messages to a seperate queue.
Thank you.

Hello Arvind,
Check SAP Note 441269.
You can monitor your queues and apply some automatic reaction when appropriate.
Maybe it can be useful.
Regards,
Diego Estanguini Gabriel

SMQ2 (Inbound Queue) : Error occurred during character conversion

Hi,
In SMQ2 an Inbound Queue has failed with status text "Error occurred during character conversion". The XML message inside this queue is in waiting status with status text " Scheduled for Outbound Processing" .
Even after cancelling this message from SXMB_MONI, and reposting the PO, still again the queue and the XML message inside the queue are in same status.
As this is in XI production system, requesting to provide some suggestion ASAP.
Thanks,
Mateen.

The queue status is still sysfail. There is only 1 message waiting in the queue.
I think that the queue might be locked for some reason and after unlocking the queue and restarting the message, the message will get processed successfully.
But before working on this I want to make sure that the queue is locked.
Do you or anyone else know how and from where can I check whether the queue is locked or unlocked?
Regards,
Mateen.

Messages stuck in SMQ2

Dear All,
I have configured a scenario Mail to PROXY Asynchronous. Process is working fine But every time transaction happen all messages are stuck in R/3 - ECC .
A developer needs to release these messages manually using SMQ2. what is the reason for this to happen every time ? Is there an alternative to skip this manual work ?
Below are the further details for the configuration done.
PI Mail Adapter (Sender )
Quality Of Service (Exactly Once)
Transport Protocol (POP3)
Poll Interval (1min)
XI Adapter (Receiver)
Transport Protocol - HTTP

Tharu Fdo,
Please check also below T-codes in ECC:
1.ST22-->ABAP Dump Analysis ,ABAP runtime errors(Proxy Code)
2.SM66-->(Background job is executed using one or multiple SAP work processes in sequence or in parallel dependent on program function and design and SAP work process is a limited critical system resource for performance like CPU and memory-Have a look at action column and identify any long running Sequential read/Direct read/insertion/updating).
3.ST12--remove the lock entries.
Mutti

SMQ2 - Inbound Queue

Every day, our inbound queue is flooded with thousands of entries from R3AD_CLASS queue. The Status is SYSFAIL, and the entries keep coming.
I'm not running anything right now that I know of and I only expect these queues when I replicate data from R/3 to SRM. I'm not replicating anything right now.
How do I stop these froming coming into the queue? Our SRM system is connected to two R/3 systems, and the queues only come from one particular R/3 system.
Thanks.
SN

The note only explains what each queue means but does not address the question that I have...why do these queues keep coming even though I'm not replicating any data from that R/3 system. They're flooding the inbound queues and how do I turn them off?
Thanks.
SN

Messages stuck in QRFC inbound and outbound queues by system error

Hi Experts,
We faced a big problem in our PI server which stopped all the traffic in the iDoc to File interface. Both the QRFC queues (inbound - SMQ1 as outbound - SMQ2) where stuck by a system error.
In IDX5 of PI we saw two inbound iDocs on exact the same date/time of creation. Both iDocs are displayed in SXMB_MONI with the status "Canceled - Since Already Processed". The output files of both iDocs are generetad on the outbound side.
The output files are genereted with a date/time stamp in filename exactly as: "pi_20101106-221812-437.dat" and "pi_20101106-221812-438.dat". So it seems that both processes where running on exact the same time.
When looking into the system error we see the following details:
com.sap.engine.interfaces.messaging.api.exception.DuplicateMessageException: Message Id 00505697-181b-1ddf-babd-68f1ac208528(INBOUND) already exists in duplicate check table: com.sap.sql.DuplicateKeyException: [200]: Duplicate key
This caused that the QRFC queues where both stuck in inbound as outbound with a SYSERROR, so PI stopped and the queues should be reactivated manually.
Does anybody have some idea of the real cause of this error. We really want to prevent such situation in the future.
Thanks in advance!
Best regards,
Joost

Hi Joost,
Are you using an adpater module to avoid the same file name processed by the receiver channel ???
If this is the case change the filename and retest flow otherwise remove the module (ex: localejbs/AF_Modules/MessageTransformBean - Local Enterprise Bean) from the channel check it whether the file getting processed or not...
OR...you have an incorrect module configuration in the receiver channel.
Do not remove the standard SAP module and make sure that you add additional modules before it.
cheers,
Ram.

EWM : Error message in the in Inbound Queue

During the creation of Inbound delivery in EWM through QRFC..the queue is stuck with an error message
" Error accessing product data administration "Message no. /SCDL/AF032""..Please let me know if you have seen this issue earlier.
ECC: Inbound delivery is created
QRFC: Stuck in the queue and error message can be seen through SMQ2 transaction
EWM: No IBN created because of the errored queue
Thanks,
Syed Ismail
PS: Is there a way to create a new section for EWM queries so that they do not get mixed up with regular WM issues ?

Thank you for your reply. The views are extended and i did look at the SCU set up and they seem to be good. Actually the scenario is that we had a system where all these processes were working fine in a client. A client copy was made to a new system and i am facing issues simulating in the new client.
I faced an issue in the new system where the function module to create IDN and ID itself was not getting determined and it was because of logical system issue in EWM>Interfaces>ERP Integration>Goods movement>Map storage locations ERP and EWM..I have corrected and the queue gets processed now but i run into this new error.
Will investigate a little more and see how it goes...
I have checked out different settings but i was still not able to fid a solution..Did anybody see this kind of message earlier ?

How to check the messages stuck up in the queues.

hi experts,
i have implemented the message queues in the EOIO form. if any message is stuck up in the inbound or the outbound queue. where would i will be able to check it.
i have the answers of checking it up in SXMB_MONI and runtime workbench.
is there any other way where i can get info about where the message has stuck up
regards,
Alpa.

Hi,
you could use transactions SMQ1 and SMQ2.
For more information:
XI Asynchronous Message Processing: Understanding XI Queues -Part I
http://help.sap.com/saphelp_nw04/helpdata/en/7b/94553b4d53273de10000000a114084/frameset.htm
Regards
Patrick
Edited by: Patrick Koehnen on Oct 22, 2008 2:51 PM

Message stuck in Adapter Engine queue with status "Delivering"

Hi All,
I have a File to File EOIO scenario. The messages are sucessfully delivered from IE to AE. All entries have a chequered flag in SXMB_MONI. No messages are stuck in IE queue (SMQ2). But the message is stuck in AE queue with status "Delivering". I can not resend or cancel the message coz the status is "delivering".
The reason it is in "delivering" status is due to some config error that I made in Communication Channel FTP parameters. Now it is corrected. But how do I deal with this message now?
Restart of server is not an option here. Is there are place I can delete the message from AE queue?
Thanks
Jaishankar

You can see the queues status (and number of stuck entries etc) through the link:
http://<host>:<port>/MessagingSystem/monitor/systemStatus.jsp
There, you can maintain the queues.
There is also a link for the EOIO Sequence Monitor:
http://<host>:<port>/MessagingSystem/monitor/sequenceMonitor.jsp
There you can see the stuck messages and maintain these.
Make sure to handle the proper message IDs.
All of these are acessible through the Messaging System main page:
http://<host>:<port>/MessagingSystem/
Regards,
Henrique.

SMQ2 Inbound Queue TIME_OUT dump

Hi all,
When we try to run SMQ2 transaction, it is resulting in TIME_OUT error. Hence nor we are able to view the entries, neither we can delete them. We also dont know from where the entries are being received. All the RFC connections are working fine. We are sure that there are large number of entries being CFIed. Please provide us a solution on how to resolve this dump. Is there any thing that should be done with LUWs?
Thanks in Advance,
Varun

23.09.2011     11:01:58     010     C     TIME_OUT               SAPLIRFC     2
What happened?
The program "RSTRFCM3" has exceeded the maximum permitted runtime without
interruption, and has therefore been terminated.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
After a certain length of time, the program is terminated. In the case
of a work area, this means that
- endless loops (DO, WHILE, ...),
- database accesses producing an excessively large result set,
- database accesses without a suitable index (full table scan)
do not block the processing for too long.
The system profile "rdisp/max_wprun_time" contains the maximum runtime of a
program. The
current setting is 1800 seconds. Once this time limit has been exceeded,
the system tries to terminate any SQL statements that are currently
being executed and tells the ABAP processor to terminate the current
program. Then it waits for a maximum of 60 seconds. If the program is
still active, the work process is restarted.
successfully processed, the system gives it another 1800 seconds.
Hence the maximum runtime of a program is at least twice the value of
the system profile parameter "rdisp/max_wprun_time".
How to correct the error
You should usually execute long-running programs as batch jobs.
If this is not possible, increase the system profile parameter
"rdisp/max_wprun_time".
Depending on the cause of the error, you may have to take one of the
following measures:
- Endless loop: Correct program;
- Dataset resulting from database access is too large:
Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table
(for example);
- Database has an unsuitable index: Check index generation.
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"TIME_OUT" C
"RSTRFCM3" or "RSTRFCM3"
"SHOW_FILE_VIEW"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
   To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.
3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.
We are getting the error only for this transaction.
We are facing this issue from Friday.
We are not able to retrieve the queue list. Instead after 1800 seconds, the transaction is resulting in TIME_OUT error.
Edited by: Nuravc on Sep 26, 2011 7:42 AM
Edited by: Nuravc on Sep 26, 2011 8:16 AM

Message stucked at O/B queue in ECC

Dear All,
We have a scenario - Purchase Order Data posted from ECC to SRM system through PI using Proxy.
Problem is when the message is triggered from ECC, it was stucked up at O/B queue in ECC in MCEXO2 queue and the entry was not found in SXMB_MONI in ECC.
Could you please suggest us resolution.
Thanks & Regards,
Soumya.

Dear All,
In SMQ1, select the Q, Unlock & Activate. When we click on activate system issues the message u201CLUWs in status NOSEND must be picked up by the application u2013Message No :: SR082 u201C.
What does that mean ? Can anybody suggest What are we missing ?
Regards,
Soumya.

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

Messages stuck in SMQ2 Inbound Queue.

Similar Messages

Maybe you are looking for