HOWTO: ensure init and close ordering plays well with recovery

A common mistake is not tuning the init and shutdown ordering of your connection pools versus the transaction kernel - so please make sure you avoid this pitfall:

If you start the transaction core before you start the pools, then the transaction recovery will not be able to get connections for recovering yet. This is not ideal.

Also, more serious: if you close the pools before the transaction core has shutdown then some in-flight transactions may not get a chance to terminate naturally, leaving them in-doubt in the back-end resource. This needlessly increases the need (and risk) for timely restart and recovery.

ExtremeTransactions (our commercial offering) has built-in integrations with Tomcat and Spring to make this work seamlessly - so you can rest on both ears. Contact us if you would like to set this up…