Ex­tremeTrans­ac­tions 3.8.0

Th­ese are the re­lease notes for Ex­tremeTrans­ac­tions 3.8.0.

83620: OSGi woes with ATE 3.7.0

Im­proved ex­ports in our OSGi bun­dle - for im­proved OSGi com­fort.

70899: Im­ple­ment log­ging API

As of this re­lease, we no longer use our pro­pri­etary log­ging con­fig­u­ra­tion mech­a­nism. In­stead, we now use your ap­pli­ca­tion's log­ging mech­a­nism/frame­work by con­fig­ur­ing a log­ger for com.atom­ikos or nest­ed pack­ages. This also yields bet­ter per­for­mance be­cause w e no longer log to two des­ti­na­tions (our in­ter­nal tm.out and oth­er) but rather to one.

61595: Doc­u­ment: poolSize over­rides minPoolSize and maxPoolSize

Im­proved poolSize javadoc.

69383: Ex­am­ple app for OSGi

The ex­am­ples for Ex­tremeTrans­ac­tions now con­tain a work­ing OSGi ex­am­ple.

80529: JDK log­ging messed up in Tom­cat we­bapps

Pri­or to this re­lease we re­lied on the JDK log­ging API. Due to a built-in lim­i­ta­tion of the JDK log­ging, Tom­cat-based tm.out files would of­ten be messed up. This should now be fixed, by al­low­ing you to se­lect a dif­fer­ent log­ging strat­e­gy like log4j or log­back.

89213: Im­prove per­for­mance of String pro­cess­ing

Var­i­ous tun­ing in­ter­ven­tions on String pro­cess­ing to im­prove per­for­mance here and there.

88660: De­stroy­ing pool: log as INFO, not WARN

The fact that the pool is be­ing de­stroyed should not be a warn­ing but rather an in­for­ma­tion­al log en­try. This has now been im­ple­ment­ed as such.