135326: Doc­u­ment JMX con­fig­u­ra­tion of log lev­el for log­back

The con­fig­u­ra­tion de­tails to al­low JMX-lev­el changes of the log lev­el have been added to the spring JMX ex­am­ple and to the wiki doc­u­men­ta­tion.

135327: Show heuris­tic mes­sages in LogUtil

The LogUtil ap­pli­ca­tion now also shows any heuris­tic mes­sages.

135290: XARe­source.com­mit(): re­fine INFO log­ging

When warn­ings are not ap­pro­pri­ate, com­mit-lev­el are logged is INFO any­way - to al­low di­ag­nos­ing the de­tails by our sup­port team.

135291: XARe­source.roll­back() and XARe­source.pre­pare() re­fine ex­cep­tion log­ging

Ex­cep­tions are now treat­ed with­out warn­ings when pos­si­ble - as in case 135274 and case 135291 and case 135290.

135493: AtomikosDataSourceBean - log warn­ing only if maxPoolSize equals de­fault size

We now log a warn­ing only if the maxPoolSize equals the de­fault (rather than the minPoolSize).

135274: XARe­sourceTrans­ac­tion.com­mit(): re­fine warn­ings on er­ror

Avoid use­less log warn­ings and stack traces if there are er­rors on com­mit that are not anom­alies in the trans­ac­tion out­come.

135247: 1-phase com­mit: treat XAER_NOTA as Roll­back­Ex­cep­tion

Dur­ing 1-phase com­mit, some JMS bro­kers (Ac­tiveMQ and oth­er?) some­times fail to recog­nise the Xid be­ing com­mit­ted. In­stead of rais­ing a need­less heuris­tic (haz­ard) ex­cep­tion, this is now treat­ed as in­ter­nal time­out/roll­back in the re­source, and mere­ly yields a Roll­back­Ex­cep­tion in­stead.

This is im­por­tant when used with Spring's mes­sage lis­ten­er con­tain­ers be­cause Spring will at­tempt to com­mit if there is no mes­sage on the queue, lead­ing to a 1-phase com­mit where this can hap­pen.

135035: Ex­tend XARe­sourceTrans­ac­tion.toString() to show ex­tra de­tails

To im­prove the in­ter­pre­ta­tion of the out­put of our LogUtil, it helps if ex­tra de­tails are shown - so the toString() method now re­turns out­put like this:

XARe­sourceTrans­ac­tion: 7075626C697368657230303030313030303031:7075626C69736865723131 [IN_DOUBT in re­source amq1]

133294: Al­low java.lang.Ob­ject meth­ods af­ter JDBC/JMS con­nec­tion is closed

It is now pos­si­ble to call Ob­ject meth­ods on con­nec­tions af­ter they were closed.

133321: Add log­file in­spec­tion tool so one can find in­flight trans­ac­tions af­ter JVM shut­down

By run­ning com.atom­ikos.logutil.LogUtil (in mod­ule trans­ac­tions-logutil) you can find any ac­tive trans­ac­tions from a giv­en log­file. Use the com­mand java -jar trans­ac­tions-logutil-3.9.16.jar to launch...

128766: Add Spring mod­ule to en­force prop­er init and close or­der among beans

We now of­fer the AtomikosAp­pli­ca­tionCon­tex­tAware class in pack­age com.atom­ikos.spring to au­to­mate the init and close or­der­ing of your Atomikos Spring beans. It au­to­mates the cor­rect init and shut­down or­der­ing of your Atomikos beans, free­ing you from the need to spec­i­fy ex­plic­it and brit­tle de­pends-on bean de­pen­den­cies, as well as init and de­stroy meth­ods. To use this fea­ture, sim­ply add an in­stance of com.atom­ikos.spring.AtomikosAp­pli­ca­tionCon­tex­tAware to your Spring con­fig...