Getting Run-time error "TIME_OUT" occurred

[Former Member]

Hello Everybody,

In my Solution manager Development system every day when I check ABAP Runtime errors using ST22 transaction code I am getting a runtime error of TIME_OUT.I has also searched the SAP notes but I am not getting a proper solution to my issue of TIME_OUT.Please suggest solutions to overcome of my above mentioned issue.Below is the log for runtime error"TIME_OUT" :

Short text

Time limit exceeded.

What happened?

The program "/BDL/SAPLBDL4" has exceeded the maximum permitted runtime without

interruption and has therefore been terminated.

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

Error analysis

After a specific time, the program is terminated to make the work area

available to other users who may be waiting.

This is to prevent a work area being blocked unnecessarily long by, for

example:

- Endless loops (DO, WHILE, ...),

- Database accesses with a large result set

- Database accesses without a suitable index (full table scan)

The maximum runtime of a program is limited by the system profile

parameter "rdisp/max_wprun_time". The current setting is 600 seconds. If this

time limit is

exceeded, the system attempts to cancel any running SQL statement or

signals the ABAP processor to stop the running program. Then the system

waits another 60 seconds maximum. If the program is then still active,

the work process is restarted.

to correct the error

Programs with long runtime should generally be started as background

jobs. If this is not possible, you can 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 unsuitable index: Check index generation.

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"TIME_OUT" " "

"/BDL/SAPLBDL4" or "/BDL/LBDL4U01"

"DO_GENERATION"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

System environment

SAP-Release 700

Application server... "sapsm4dev"

Network address...... "10.102.10.34"

Operating system..... "Windows NT"

Release.............. "5.2"

Hardware type........ "2x Intel 80686"

Character length.... 8 Bits

Pointer length....... 32 Bits

Work process number.. 0

Shortdump setting.... "full"

Database server... "SAPSM4DEV"

Database type..... "ORACLE"

Database name..... "SMD"

Database user ID.. "SAPSR3"

Char.set.... "English_United State"

SAP kernel....... 700

created (date)... "Oct 23 2007 00:57:10"

create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"

Database version. "OCI_10201_SHARE (10.2.0.1.0) "

Patch level. 133

Patch text.. " "

Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."

SAP database version. 700

Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows

NT 6.0"

Memory consumption

Roll.... 8112

EM...... 2090592

Heap.... 0

Page.... 16384

MM Used. 1516976

MM Free. 572168

Thanks and Regards,

Ashish Thakkar.

[chi_chiu_wong]

Dear all,

Please take note that parameter rdisp/max_wprun_time is no longer valid for latest S/4HANA system.

You may check for ABAP Dump message in Error Analysis for the latest parameter (i.e. rdisp/scheduler/prio_high/max_runtime ) to be used for tuning.

Example of ST22 (TIME_OUT) -- Error Analysis

Error analysis

Once the maximum runtime is exceeded, the program is aborted. This serves to prevent work processes being blocked for an unnecessarily long period of time, for example by - endless loops (DO, WHILE, etc.) - lengthy database accesses . The maximum runtime of a program is set by profile parameter "rdisp/scheduler/prio_high/max_runtime". The current setting is 660 seconds. If the current setting deviates from the value of the parameter in question, the application has set the maximum runtime itself. Once the maximum runtime is exceeded, the program is aborted.

Example of Parameter Description:

Parameter

rdisp/scheduler/prio_high/max_runtime

Short text

Maximum runtime for high priority dialog requests

Parameter Description

This parameter limits the time for which a high-priority request can run uninterrupted in a dialog work process before it is forced to terminate. Interruptions, that is, activities that could lead to a work process switch (roll-out) (for example, WAIT statements or RFC calls) each restart the time interval at zero.

When combined with the parameters for the other priorities (see rdisp/scheduler/prio_*/max_runtime), it makes it possible to distinguish the maximum runtimes using the priorities.

The system assigns high priority to all dialog requests that are directly triggered by user interaction (GUI, RFC remote logon through SM51), and to all system requests (everything that runs in the dialog work process and is not GUI, HTTP, or RFC).

The intention behind this parameter is mainly defensive. It limits the consequences of an activity unintentionally running for a long time: it means that a hanging request or a programming error cannot indefinitely block a dialog work process that is intended for high priority activities.

Choose a value that allows enough time for correctly-running high priority requests to be processed, even under load.

After the maximum runtime has expired, the program terminates at two levels:

• If the program is currently executing ABAP commands, the ABAP processor terminates the program.

• If the program is hanging in an external command, such as SQL, the entire work process is terminated after a second time period of a maximum of 60 seconds, and the user context is reset after the process restart.

An ABAP short dump is generated in both cases.

In the case of HTTP requests, remember that there is a second timeout (see the subparameter PROCTIMEOUT of the parameter icm/server_port).

To prevent double timeouts, the default value of this parameter is set slightly lower than the value of the parameter rdisp/scheduler/prio_high/max_runtime. Remember this when making changes to the configuration.

Application Area

Dispatcher

Parameter Unit

The unit can be specified as seconds, minutes, hours, or days by adding 's', 'm', or 'h' . There can be spaces between the value and the unit. Specifications without a unit are interpreted as seconds. If not value is specified, the runtime is unlimited.

Default Value

11m

Who is permitted to make changes?

Customer

Operating System Restrictions

None

Database System Restrictions

None

Are other parameters affected or dependent?

rdisp/scheduler/prio_normal/max_runtime

rdisp/scheduler/prio_low/max_runtime

icm/server_port

Values allowed

n [unit] where

• n >= 0

• Unit = S | M | H | D

[former_member185327]

Hi Everyone, Although it's an old thread but I would like to share the info which helped us. We have increased the size of the parameter abap/shared_objects_size_MB from by default_vale 250 to 400 MB. Thanks and Regards Anurag Das

[Former Member]

In SAP, there is a parameter rdisp/max_wprun_time which limits the maximum permitted runtime without interruption. By default this value is set to 600 seconds. However, if you are frequently encountering more dumps in SAP system due  to this, you can consider increasing this value to 3600 seconds to avoid this issue.

[Former Member]

Hi

Maximum work process runtime exceeded, due to which this runtime error occurs.

Check for all the background jobs which got cancelled during the period of dump.

You will get the clue of error.

Rahul

[Former Member]

Hi,

>Check for all the background jobs which got cancelled during the period of dump.

Hmmm, Maximum process runtime only apply to dialog processes. Hopefully we don't get time outs for batch jobs !

Regards,

Olivier

[Former Member]

Yup. My Bad. I apologize for incorrect info.

Thanks Olivier.

Rahul

[Former Member]

Hi Olivier,

Thanks for replying but I had already checked the background jobs and none of the background jobs get cancelled during the period when dump occurs as well as for the everydayday when this dump occurs.

Please suggest some more solutions to overcome of the short dump which I am facing in my Solution Manager Development System.

Thanks and Regards,

Ashish Thakkar.

[Former Member]

Hi,

If your parameter rdisp/max_wprun_time is really 600 s, that's 10 minutes wich should be plenty enough.

If you get a lot of time out short dumps, you have to check if they are from a specific transaction or report.

If the short dumps are for all transactions/reports, then you have definitevly a problem in your system.

Regards,

Olivier

[Former Member]

Hi Olivier,

In my Solution manager DEV.System ;parameter rdisp/max_wprun_time is already set to 600 s.I am getting the dump of"TIME_OUT" only once in a day in my system and is due to the report"/BDL/SAPLBDL4" also I had tried to find out the background job which is using this report but not found the background job which is using this report but there is background job "/BDL/TASK_PROCESSOR" using report "/BDL/TASK_SCHEDULER" which is finishing perfectly in my system .Is there any relation between report"/BDL/SAPLBDL4" and report"/BDL/TASK_PROCESSOR" .

Thanks and Regards,

Ashish Thakkar.

[Former Member]

Ashish

Check the SM21 entries at the time when runtime error occurs. Try figure out what activity starts or ends at that time. You might get some useful information from log entries.

Rahul

[dasistdochscheisse]

Background jobs do not have a time out.

Dialogue processes have a time out. A description can be found in RZ11 in the documentation of the parameters

rdisp/max_wprun_time ( this one is mentioned in the error description)

In newer releases:

rdisp/scheduler/prio_high/max_runtime
rdisp/scheduler/prio_normal/max_runtime

rdisp/scheduler/prio_low/max_runtime