Ex­tremeTrans­ac­tions 3.7.3

Th­ese are the re­lease notes for Ex­tremeTrans­ac­tions 3.7.3

84252: Hide warn­ing on forceCloseAl­lPend­ingS­tate­ments

The log­ging noise in JDBC has been re­duced sig­nif­i­cant­ly.

84253: Log warn­ing in XARe­sourceTrans­ac­tion if er­rors on pre­pare

Added warn­ing to the log if pre­pare yields er­rors.

91719: UserTrans­ac­tionFac­to­ry (JNDI): re­turn UserTrans­ac­tionMan­ag­er rather than UserTrans­ac­tion

This should make out-of-the-box in­te­gra­tion with Tom­cat and Spring eas­i­er.

96003: Bug in Jm­sSen­derTem­plate: for unan­tic­i­pat­ed ex­cep­tions dur­ing send, con­nec­tions are not re­turned to pool?

Im­proved the way that un­ex­pect­ed er­rors are dealt with: the con­nec­tions should be closed in those cas­es also.

86014: This UserTrans­ac­tionMan­ag­er in­stance was closed al­ready

Im­proved be­hav­ior af­ter close: only be­gin() now throws an ex­cep­tion. The oth­er JTA meth­ods are al­lowed to pro­ceed with the in­ten­tion of max­i­miz­ing the chance of clean shut­down.

89030: Dead­lock in JMS con­nec­tion pool­ing mech­a­nism

Re­moved syn­chro­niza­tion is­sues among con­cur­rent threads that could cause a dead­lock.

93853: Sin­gleThread­edJm­sSen­derTem­plate does not re­cov­er from ses­sion er­ror?

This should now also be fixed.

95466: Dead­lock in trans­ac­tions-mes­sag­ing

Fixed a dead­lock sit­u­a­tion dur­ing shut­down.

80653: En­list­ing two XARe­sources via JTA API fails for same back­end

Check­ing for en­list­ed XARe­sources has been re­laxed to al­low more use cas­es than be­fore.

95823: XARe­sourceTrans­ac­tion.re­freshCon­nec­tion fails af­ter re­cov­ery

Fixed a bug where haz­ard XA branch­es could not ter­mi­nate due to con­nec­tiv­i­ty fail­ures af­ter restart.

95886: Co­or­di­na­torImp.re­cov­er() re­turns false in the wrong cas­es

Im­proved the way re­cov­ery di­ag­noses it­self - to avoid un­nec­es­sary log warn­ings.

85463: Bug in check­point­ing: the last im­age flushed is not tak­en into ac­count

This has been fixed.