As per the Jira's database tuning page, there is no mention of numTestsPerEvictionRun which is part of jdbc BasicDataSource Configuration Parameters

• numTestsPerEvictionRun (3) - The number of objects to examine during each run of the idle object evictor thread (if any).

The Apache documentation default this setting to 3 currently, but the parameter is mentioned in the below article to be set to <pool-max-size>

• Operations in Jira server fail with communications link failure in logs with MySQL

Can we update the database tuning page to include numTestsPerEvictionRun and provide recommendation on the default value?