SMQ2 Inbound Queue TIME_OUT dump

Question

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

Answer 1

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