Ex­tremeTrans­ac­tions 4.0.67

170331: Add con­nec­tionVal­i­da­tionIn­ter­val so JDBC con­nec­tion val­i­da­tion will be re­peat­ed every X mil­lisec­onds

You can now set the in­ter­val af­ter which JDBC con­nec­tion val­i­da­tion should be re­peat­ed, so users can have an ap­pli­ca­tion-spe­cif­ic im­pact on per­for­mance.

170195: Tom­cat JNDI in­te­gra­tion: al­low set­ting XADataSource via JNDI

Sim­i­lar to JMS, we added the ca­pa­bil­i­ty to spec­i­fy the XADataSource as a JNDI ref­er­ence in Tom­cat.

170194: Tom­cat JNDI in­te­gra­tion: al­low set­ting ven­dor XA con­nec­tion fac­to­ry via className

Sim­i­lar to JDBC, we now also al­low spec­i­fy­ing the XA ven­dor set­tings via the class name (in­stead of only the JNDI ref­er­ence).

164168: Con­nec­tionPool's onXPooledCon­nec­tionTer­mi­nat­ed method: pub­lish event out of syn­chro­nised block

Another in­cre­men­tal per­for­mance op­ti­mi­sa­tion to max­imise per­for­mance.

Warn­ing: Known Is­sues With REST De­mos

Some of the REST demos don't work in this re­lease - this will be fixed in an up­com­ing re­lease. This will only af­fect de­vel­op­ment projects that are test­ing REST trans­ac­tions.

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