Ex­tremeTrans­ac­tions 3.8.2

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

105547: Time­out of ac­tive trans­ac­tion gen­er­at­ing too much log con­tent

We now avoid gen­er­at­ing too much log con­tent for time­outs.

72744: Does max_ac­tives also take re­cov­ered co­or­di­na­tors into ac­count?

Fixed a con­di­tion where re­cov­ery could lead to out-of-mem­o­ry er­rors.

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.

86779: Add op­tion­al prop­er­ty to NOT set time­out on XARe­source so Or­a­cle er­rors are avoid­ed on re­cov­ery

The new 'prop­a­gateJ­taTime­outToXaRe­source' con­fig­u­ra­tion prop­er­ty for JDBC and JMS now al­lows you to dis­able time­outs prop­a­gate via XA. For some ven­dor's XARe­soure im­ple­men­ta­tions this time­out seems to give prob­lems and this prop­er­ty can serve as a workaround.

This was for a de­vel­op­ment team had no in­flu­ence on the XA set­tings of the Or­a­cle data­base (owned by the DBA team). The JTA/XA time­out they used seemed to con­flict with the in­ter­nal Or­a­cle time­out set­tings, so they got lots of er­rors on re­cov­ery af­ter a restart. This caused their project to look bad.

Since there was no con­trol over their Or­a­cle, this gave them a workaround to (at least) not in­ter­fere with trans­ac­tion time­outs in Or­a­cle. This meant they could avoid get­ting blamed by the DBAs for set­ting “bad" time­outs. We have no oth­er record of oc­cur­rence, so it looks like this was not a com­mon is­sue and un­like­ly some­thing we can im­prove or change in our prod­uct. But we did want to al­low users to tune / tweak XA some­what in sim­i­lar cas­es, be­cause dif­fer­ent ven­dors some­times have dif­fer­ent in­ter­pre­ta­tions. Which brings us to the next fea­ture be­low...

81146: Sup­port ven­dor-spe­cif­ic flags on XARe­source

Ven­dor-spe­cif­ic flags for start­ing a new XA branch as well as join­ing/sus­pend­ing/re­sum­ing/end­ing an ex­ist­ing branch are now sup­port­ed on the JDBC and JMS con­nec­tor class­es.

102830: Avoid log­ging user names and pass­words in plain text

The new prop­er­ty 'xaProp­er­tyNamesToHide' al­lows you to spec­i­fy what ven­dor-spe­cif­ic XA prop­er­ties should be hid­den in the log en­tries. Typ­i­cal­ly, this would be used for sen­si­tive in­for­ma­tion like pass­words.