My Oracle Support Banner

How to find connection parameters for clients which override global timeout variables (Doc ID 2524988.1)

Last updated on APRIL 12, 2022

Applies to:

MySQL Server - Version 5.7 and later
Information in this document applies to any platform.


If the session level values are greater than the global(s) for wait timeout, then these sessions may need to be manually killed before they become an issue for resourcing on a busy server.

An Example scenario can be one where the global values for wait_timeout / interactive_timeout are set quite low ( the default value is 8hours ), eg 1800 seconds for OLTP.

If the environment is heterogeneous and there are many different applications / users connecting to the DB, some may explicitly set the default values at the session level.

Currently by design , this will override the global value and in the specific case for timeouts, the clients will be able to reaming connected to the DB for longer that the DB global value.

This can be seen to have the potential to impact the DB's resources and therefor ongoing stability.

While manually killing the jobs might address the short term goal of reducing the open connection count, the DBA will want to contact the applicaiton administrators to have them update their session variables to better reflect the environment.

This information can be obtained from the SHOW GLOBAL PROCESSLIST for any idle threads grater than the server's global default.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.