[IDEA] Expose all properties of the underlying DB connection pool

[leite08]

Is your feature request related to a problem? Please describe.

Establishing a database connection takes time, so DB connection pools have a configuration to set a minimum number of connections to be running at all times. This way, when new requests come the application can make use of already created DB connections without having to wait for a connection to be established.

Currently, Mirth only exposes a max-connections property - https://docs.nextgen.com/bundle/Mirth_User_Guide_4_4_0/page/connect/connect/topics/c_The_mirth_properties_File_connect_ug.html, so one can't specify the number of DB connections to be active at all times.

There are also other settings in a DB conn pool that one can adjust for each use case, like idle timeout

Describe your use case

We need this so we can better tweak Mirth to maximize the resources we have available.

Describe the solution you'd like

We would like to have the ability to set all properties supported by the underlying DB connection pool.

But, at minimum, expose a new property so we can set the minimum number of DB connections to be active at all times.

Describe alternatives you've considered

There's none.

Additional context

It seems this is the underlying DB connection pool: https://github.com/brettwooldridge/HikariCP?tab=readme-ov-file#gear-configuration-knobs-baby

[leite08]

This started with this discussion: #6117

And got confirmation from folks on Slack that this is not yet possible and so could be a feature request.