Ex­tremeTrans­ac­tions 3.8.7

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

130852: UniqueIdM­gr: java.lang.Run­timeEx­cep­tion: Al­ready writ­ing a new ver­sion

Fixed cleanup of re­sources when writ­ing a new epoch file, to avoid ex­cep­tions un­der ab­nor­mal op­er­at­ing con­di­tions.

123322: Avoid log­ging over­head for (root) trans­ac­tions with only one par­tic­i­pant

Trans­ac­tions with only 1 par­tic­i­pant (or re­source) will re­sort to 1-phase com­mit and there is no way to re­cov­er their state. There­fore, log­ging adds use­less over­head and is now avoid­ed.

123291: Un­ex­pect­ed XAEx­cep­tion er­rorCode dur­ing 2PC com­mit: call re­cov­er() to find out if retry makes sense

We now try to avoid un­nec­es­sary and an­noy­ing Heuris­ticHazard out­comes and dito re­tries, by do­ing ex­tra checks in the XARe­source back­end when­ev­er pos­si­ble.

123502: Dead­lock on mul­ti-thread­ed JMS con­nec­tion use

Fixed a dead­lock con­di­tion when mul­ti­ple threads use the same JMS con­nec­tion, each in its own ses­sion.

126795: Nul­lPoin­t­erEx­cep­tion dur­ing bor­rowCon­nec­tion in JMS with con­cur­rent close of ex­ist­ing ses­sion

Fixed a NPE con­di­tion where con­cur­rent bor­row re­quests and close op­er­a­tions on ex­ist­ing ses­sions would in­ter­fere.