Ex­tremeTrans­ac­tions 5.0.94

182106: Im­prove Trans­ac­tionSer­vice shut­down: co­or­di­na­tor dis­pose should wait for ac­tive timer threads

We im­proved shut­down to wait for ac­tive timer threads, so there are less warn­ings in Tom­cat in­stal­la­tions (con­cern­ing pend­ing threads and pos­si­ble mem­o­ry leaks).

182134: Make lo­calTrans­ac­tionMode = true by de­fault (for JDBC)

We've re­vert­ed a de­ci­sion we made when re­leas­ing the 5.0: lo­calTrans­ac­tionMode should not be false (by de­fault) but rather true. This is to avoid back­ward com­pat­i­bil­i­ty is­sues with ex­ist­ing in­stal­la­tions that want to up­grade.

182161: Pool prob­lem with Shad­ow JDBC dri­ver

We fixed an in­com­pat­i­bil­i­ty in the way our pooled con­nec­tions are ini­tialised and a Shad­ow JDBC dri­ver lim­i­ta­tion.

182138: RestTrans­ac­tionSer­vice: im­proved re­cov­ery

We im­proved dis­trib­uted re­cov­ery for com.atom­ikos.re­mot­ing.taas.RestTrans­ac­tionSer­viceImp.

182132: De­fault­Ex­port­ingTrans­ac­tionMan­ag­er: au­to­mat­i­cal­ly add URL of re­cov­ery co­or­di­na­tor to Prop­a­ga­tion

We have im­proved re­mot­ing re­cov­ery by au­to­mat­i­cal­ly adding the URL of the re­cov­ery co­or­di­na­tor. Pre­vi­ous­ly this re­quired set­ting a sep­a­rate man­u­al start­up prop­er­ty.

181667 / 181668: Im­proved how re­mot­ing re­cov­ery deals with time­outs

Aban­doned or heuris­tic trans­ac­tions should not delete the re­mote par­tic­i­pant in­for­ma­tion - so re­mot­ing re­cov­ery can still do its job.

182099: JMS: cre­ateCon­nec­tion(user, pass­word) should log a warn­ing

We pre­vi­ous­ly low­ered the log to DEBUG. For cus­tomers that don't want a warn­ing, please:

1. Sub­class AtomikosCon­nec­tionFac­to­ryBean
2. Over­ride this method to not log a warn­ing

182041: Add DEBUG logs to Batch­ingMes­sageLis­ten­erCon­tain­er

We added de­bug logs to make it eas­i­er to see if batch­ing is work­ing.

181866: Im­prove re­mot­ing re­cov­ery to avoid re­mote calls if there is a shared LogCloud DB

When a shared DB is used, all in­for­ma­tion is present in the DB it­self - so re­mote http calls are not need­ed. This has been im­ple­ment­ed for re­cov­ery of im­port­ed trans­ac­tions.

Only for cus­tomers. Not a cus­tomer yet?