Ex­tremeTrans­ac­tions 3.9.32

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

Avail­able to cus­tomers only. Want to be­come a cus­tomer?

Send me a quote

I have read and ac­cept the pri­va­cy pol­i­cy.

Mes­sage: Please send me a quote for Ex­tremeTrans­ac­tion­s3­dot9­dot32 Date: 29 May 2026 - 22:02 Email: !!ad­dress!! Re­mote-Host: 216.73.216.244

147443: Add sup­port for Log4j2

Added au­to­mat­ic de­tec­tion of Log4j2 in the class­path

24346: AtomikosDataSourceBean prop­er­ty to avoid TMJOIN by de­lay­ing XARe­source.delist­ment un­til com­mit time

The more ex­ot­ic TMJOIN be­hav­iour is now dis­abled when set­ting sup­port­sTmJoin=false on the AtomikosDataSourceBean class. This in­creas­es com­pat­i­bil­i­ty with SQLServ­er and also in­creas­es per­for­mance for trans­ac­tions that have mul­ti­ple state­ments go­ing to the back­end with "ag­gres­sive con­nec­tion re­lease" in ORM tools like Hiber­nate.

149031: JDBC purge closed state­ments: avoid loop­ing if dri­ver does not sup­port isClosed

When the JDBC dri­ver does not sup­port the isClosed method then the list of open state­ments will keep grow­ing in the Ab­strac­tCon­nec­tionProxy class. This in turn will lead to ex­pen­sive and use­less it­er­at­ing over an ever-grow­ing list of state­ments for every state­ment be­ing cre­at­ed. This is bad for per­for­mance and caus­es up to 80% of the ex­e­cu­tion time be­ing spent in the purg­ing method do­ing use­less it­er­a­tions.

We now stop try­ing as soon as the isClosed call throws any ex­cep­tion. While the list of state­ments still keeps grow­ing, we at least avoid it­er­at­ing use­less­ly.

148782: MSDTC crash­es with ag­gres­sive con­nec­tion re­leas­ing and ex­ten­sive TMJOIN us­age

MSDTC cre­ates "or­phaned" re­sources on the XACon­nec­tion when TMJOIN is used. With a lot of these, the MSDTC serv­er can crash. You can now avoid this by set­ting sup­port­sTmJoin=false on the AtomikosDataSourceBean.