SAPGui Maximum runtime exceeded

Systems you work with have a timeout parameter. You may be logged on or an anonymous user, in both cases the system creates a session for you and controls its lifetime. This is not to remind you to get your work done rapidly, but mostly to ensure that a long living session is not eating up too much resource (so, short, yes, it is to ensure you get your work done rapidly). The timeout period for a session depends on your system. Normal time is between 10 minutes to 30 minutes. In a SAP NetWeaver ABAP system, the time is set by default to 10 minutes, or 600 seconds. The counter is reset each time a commit is issued by the running ABAP program.

It can, however happen that you reach a timeout.

What to do? I have to say that my system was a little bit busy. I restarted my dev system and all went back into normal. As an alternative, you can change the timeout parameter. How to do this and why you should not do this is explained in SAP Note 25528.

  • Profile parameter: rdisp/max_wprun_time
  • Tx: RZ10 (permanent change)
  • Tx: RZ11 (only until next restart)

Set session timeout for SMP3 admin console

SMP3 runs on Tomcat, and therefore inherits its basic configuration from Tomcat. One of these is the session timeout parameter. By default, timeout is set to 20 minutes. Depending on your requirements this can be too short or too long. Changing the value is easy as you only have to change one parameter in one file and restart SMP3 to make the change take effect. The procedure is outlined at SAP Help.

The file to be changed is the Tomcat configuration file that can be found at: <SMP_HOME>\Server\config_master\org.eclipse.gemini.web.tomcat\web.xml.

The parameter to change is: session-timeout.

To increase the timeout to 1 hour, change it to 60.

Restart SMP3 to benefit from your change.