SMQ2 Inbound Queue TIME_OUT dump

[Former Member]

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

[Former Member · Accepted solution]

Hi,

Please check the time interval after which you get the TIME_OUT dump and set the following dynamically switchable parameter to fit your requirement.

rdisp/max_wprun_time

Regards,

Varun

[Former Member · Accepted solution]

Hi Both,

Actually, we need to know why the TIME_OUT occurs.

Till Thursday it was working fine.

Is there any possibility of solving this, without changing the parameter?

We need to know, why the inbound queues are not being displayed.

Please advise.

Thanks

Varun

[Former Member · Accepted solution]

Hi,

The reason for not getting the SMQ2 queue being displayed is that the runtime of the wp exceeds the time required for reading the entire queue, hence the time out dump.

It may be possible that the queue contained fewer entries the last time you tried reading it.

From the details posted earlier, the parameter value is set to 1800 secs (30 mins).

Please try increasing the parameter value to have a longer wp runtime. Since the parameter is dynamically switchable, you may increase it further, although it is not recommended to have a higher value.

Please dont forget to have the original parameter value reverted back, once you are able to view and process the queues.

Also, please refer following link, you may try reading the queue contents from the table ARFCRSTATE directly.

http://help.sap.com/saphelp_nw04/helpdata/en/d9/b9f2407b937e7fe10000000a1550b0/content.htm

Thanks.

[Former Member · Accepted solution]

Hi,

I already checked the table. There are no entries in that table.

Still we are getting the TIME_OUT dump for the transaction.

Please advise.

[Former Member · Accepted solution]

Hi,

Try to schedule the report RSQIWKEX to delete SMQ2 entries or use SMQR to delete/register the queues.

You should also check the source of the entries first and take appropriate action.

Please refer the following links:

[Former Member · Accepted solution]

Hi,

Is there any possibility of deleting entries in inbound queue or the queue itself without using SMQ2?

Any report that can be run to do this?

Regards,

Varun

[Former Member · Accepted solution]

Check whether statistics for your RFC tables are correct.

It might help to rebuild indexes for RFC tables.

What is your database?

In case of Oracle have a look at SAP Note 1020260 - Delivery of Oracle statistics (Oracle 10g, 11g).

It is about tables ARFCRSTATE and so on.

I wouldn't increase rdisp/max_wprun_time btw.

hope this helps

[Former Member · Accepted solution]

Hi All,

The issue is solved.

Action Taken:

1. Increasing the u2018rdisp/max_wprun_timeu2019 might probably help. But, this is not advisable as the increase in time might cause the system to low in performance.

2. Checking the table ARFCRSTATE as all the processed entries will be placed here and determining from where the entries are being inbounded. But, if there are inconsistencies, there will be no entry in the table.

3. All the inconsistencies in LUW should also reflect in TRFCQSTATE table. So, the report, RSTRFCEK can be run. But this will only check the Inconsistencies.

4. To delete all the queues in SMQ2, i.e., inbound queues, we need to run the RSTRFCID report.

Reference: SAP notes: 760113, 574018

Regards,

Varun

[Former Member]

Thanks all for the valuable solutions provided.

[former_member286941]

Please paste the dump contents here, not all dump but first few from dump

Short text

What happened?

What can you do?

Error analysis

How to correct the error

Information on where terminated

Is this timeout happening with other transactions also?

When this timeout error started coming?

[Former Member]

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

[Former Member]

Hi,

Increase the parameter rdisp/max_wprun_time from the t.code RZ11 .

This parameter controls the time out for a work process.

See the following link too..

Regards

Bhuban

[Former Member]

Hi,

We have also tried changing the Parameter. Still after the time, the TIME_OUT dump occurs.

Kindly, specify if this can be rectified by any other way.

Its not about the dump, we are not able to view the queues.

Please advise.

Thanks,

Varun