title: HIKARICP Killing Connections
body: <p>Can someone help me understand the Hikari implementation better. We currently have the following settings in use:</p>
  <pre><code>spring.datasource.hikari.maxLifetime=600000
  spring.datasource.hikari.maximumPoolSize=3
  spring.datasource.hikari.minimumIdle=1
  </code></pre>
  <p>What we see, is that after 10 min, the applications connections are cleared, and then, it struggles to make new connections to the DB, resulting in sessions exceeded errors, from the DB, we understand what they are, but it seems that rather than use the existing sessions, Hikari is trying to create new sessions, and the DB is not allowing that as is it supposed to.</p>
  <p>Why is Hikari trying to establish new connections and not use connections from the available sessions ont he DB?</p>
  <p>How does the maxlifetime work? reading the documents on the Hikari Git hub page, it seems straightforward enough.</p>
  <p>We have also set</p>
  <pre><code>spring.datasource.hikari.idle-timeout=10000
  </code></pre>
  <p>on the idea that it may not kill those connections quite so quickly, but it still seems to remove them...</p>
  <p>Thanks</p>