Occasionally exceptions from Hikari pool regarding Connection leak detection triggered timeouts
Occasionally we see exceptions like WARN c.zaxxer.hikari.pool.ProxyLeakTask - Connection leak detection triggered
While these warnings are not so critical, on occasions seems that we have long transactions especially between different systems when exchange messages during transactions that use the DB.
In application.yml we can adjust leakDetectionThreshold to display the warnings. In cases that we have long queries that can be ok, but in many other cases we need to watch out for transaction issues, especially since we use the jms.
in future releases we need to consider distributed transaction processing using for example Atomikos or Narayana frameworks. For now we can address several issues with some code refactoring