We have strange busy workers swing in production server in a cluster (only one of 4). At red line we restart tomcat8 and it stop swinging.
Tomcat accepts max 100 http connections and 100 jdbc connections in the pool. It seems to touch the max jdbc limit when busy workers are high. During the swing the server has bad performances.
I don't know witch direction to take :
- keepalive miss configuration ?
- change max connections
- change ratios between http / jdbc connexion (but usually http request use 1 jdbc connection)
- ??
