Ex­tremeTrans­ac­tions 4.0.72

Re­lease notes for 4.0.72...

172665: Pre­pare fail­ure: clar­i­fy er­ror log even more

Ex­pe­ri­ence has shown that fail­ures dur­ing pre­pare can re­sult in con­fus­ing ex­cep­tion mes­sages. We've tried to im­prove this even more.

172436: JDBC/JMS: clar­i­fy mes­sage if pooled con­nec­tion can­not be got­ten

Per cus­tomer re­quest, we im­proved the er­ror mes­sage if no con­nec­tion could be got­ten from the pool in both JMS and JDBC: in­stead of Failed to grow the con­nec­tion pool it now says Failed to cre­ate a con­nec­tion.

172905: Al­low tran­si­tion from PREPARING/COMMITTING/ABORTING to ABANDONED

Fixed a bug where trans­ac­tions were not cleaned up af­ter time­out - there­by pos­si­bly caus­ing a mem­o­ry leak in the core.

173314: Log num­ber of open con­texts in a pooled con­nec­tion

Added (trace-lev­el) log­ging to show the num­ber of open con­texts for a pooled con­nec­tion when the pool checks its avail­abil­i­ty.

173315: JMS cre­ateCon­nec­tion(userName, pass­word): don't log warn­ing

We no longer log a warn­ing when try­ing to cre­ate a new con­nec­tion with a cus­tom userName and pass­word. This is be­cause some frame­works de­pend on this method, which caus­es a lot of noise in the logs. In­stead, we now log this in de­bug lev­el.

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­s4­dot0­dot72 Date: 30 May 2026 - 07:13 Email: !!ad­dress!! Re­mote-Host: 216.73.217.25