Le­ga­cy sys­tems car­ry vis­i­ble costs, from main­te­nance and scarce ex­per­tise to op­er­a­tional fragili­ty. But mod­ern­iza­tion can in­tro­duce a less vis­i­ble cost: ap­pli­ca­tion-lev­el con­sis­ten­cy, com­pen­sa­tion and re­cov­ery log­ic. Here is what fi­nan­cial in­sti­tu­tions should eval­u­ate be­fore choos­ing an ar­chi­tec­ture.

A cor­rect­ness fix for JMS con­nec­tion pool­ing: con­cur­rent­ly clos­ing ses­sions of a pooled con­nec­tion can no longer dead­lock the pool, so a con­nec­tion that fails asyn­chro­nous­ly (for ex­am­ple an IBM MQ con­nec­tion drop) is re­li­ably de­tect­ed and re­placed.

Ex­tremeTrans­ac­tions 6.0.119 hard­ens crash re­cov­ery (a sib­ling-branch atom­ic­i­ty resid­ual is closed; a failed or dan­ger­ous­ly-late com­mit-log write is now treat­ed as a heuris­tic haz­ard rather than an in­cor­rect roll­back) and fix­es JMS con­nec­tion-pool reuse of a con­nec­tion bro­ken asyn­chro­nous­ly (for ex­am­ple IBM MQ). It also adds LogCloud re­cov­ery-ac­tion au­dit­ing with a read-only view­er, and cor­rects cross-ser­vice re­cov­ery and Spring Boot 3.4 con­fig­u­ra­tion. It is a drop-in re­place­ment for ear­li­er 6.0.x re­leas­es.

Two trans­ac­tion-time­out cor­rect­ness im­prove­ments: a fix so a doomed trans­ac­tion reusing the same con­nec­tion is now in­ter­rupt­ed on every sub­se­quent use, not just the first, plus a new opt-in op­tion to bound a REQUIRES_NEW trans­ac­tion's time­out to its sus­pend­ed par­ent's re­main­ing time. Also in­cludes an SLF4J 2.x de­tec­tion fix and a con­nec­tion-pool idle-evic­tion re­gres­sion fix.

Two time­out-cor­rect­ness im­prove­ments for XA en­list­ment: an opt-in guard that re­fus­es to en­list a re­source on a trans­ac­tion that has al­ready timed out or been marked roll­back-only — in­ter­rupt­ing it be­fore XA START in­stead of fail­ing lat­er at com­mit — and a fix so an al­ready-timed-out co­or­di­na­tor no longer re­sets an en­list­ed re­source's own time­out to the back­end de­fault (which held XA re­sources longer than need­ed). Plus, you can now skip the lega­cy Or­a­cle AQ forceCon­nec­tionIn­toXaMode workaround on spec-com­pli­ant JMS providers and on Or­a­cle AQ 19c and lat­er.