Need to override maxThreads settings for Confluence to prevent users seeing a Johnson on Confluence launch

Recently we have added a new Confluence Johnson warning that displays to users in the case of upgrade.
The Johnson warns in the case that the users have HTTP thread settings which are not optimal for the number of database connections they have set. Details: https://confluence.atlassian.com/confkb/startup-check-http-maxthreads-configuration-939930122.html

Confluence distribution sets maxThreads to 48 which compliments database connection pool of 60.

AMPS does not, it uses the default cargo/tomcat values.

This will not change the settings for other applications such as JIRA, Bamboo etc.