HOWTO: en­sure init and close or­der­ing plays well with re­cov­ery (Un­pub­lished)

A com­mon mis­take is not tun­ing the init and shut­down or­der­ing of your con­nec­tion pools ver­sus the trans­ac­tion ker­nel - so please make sure you avoid this pit­fall:

If you start the trans­ac­tion core be­fore you start the pools, then the trans­ac­tion re­cov­ery will not be able to get con­nec­tions for re­cov­er­ing yet. This is not ide­al.

Also, more se­ri­ous: if you close the pools be­fore the trans­ac­tion core has shut­down then some in-flight trans­ac­tions may not get a chance to ter­mi­nate nat­u­ral­ly, leav­ing them in-doubt in the back-end re­source. This need­less­ly in­creas­es the need (and risk) for time­ly restart and re­cov­ery.

Ex­tremeTrans­ac­tions (our com­mer­cial of­fer­ing) has built-in in­te­gra­tions with Tom­cat and Spring to make this work seam­less­ly - so you can rest on both ears. Con­tact us if you would like to set this up...