Ex­tremeTrans­ac­tions 4.0.74

Re­lease notes for the 4.0.74 re­lease...

175280: Trans­ac­tionMan­agerLife­cy­cleLis­ten­er: im­prove stop sup­port to avoid clos­ing re­sources for ac­tive Spring Mes­sageLis­ten­erCon­tain­ers

This lis­ten­er class for Tom­cat in­te­gra­tion used to shut­down the trans­ac­tion core on STOP events. Due to (lack of) or­der­ing dur­ing such STOP life­cy­cle event, there may still be ac­tive web ap­pli­ca­tions when this is called. As a re­sult, any re­main­ing mes­sage lis­ten­ers will start giv­ing warn­ings that the core has al­ready been shut­down, along with its JMS re­sources.

This has been fixed, at the ex­pense of a dif­fer­ent (but less in­tru­sive) warn­ing like this one:

The web application [/...] appears to have started a thread named [Atomikos:5] but has failed to stop it. This is very likely to create a memory leak.

This is due to the lim­it­ed knowl­edge the Tom­cat core has about Atomikos threads. It can be ig­nored, there is no mem­o­ry leak in this case.

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­dot74 Date: 29 May 2026 - 20:02 Email: !!ad­dress!! Re­mote-Host: 216.73.216.244