Trans­ac­tion­sEssen­tials 5.0.5

179080: JtaAwareThread­Lo­calCon­nec­tion: clos­ing proxy should not call markClosed - so re­cy­cling is al­lowed

When us­ing and clos­ing the non-XA con­nec­tions in JTA mode, reusing the same con­nec­tion in the same trans­ac­tion was im­pos­si­ble due to the con­nec­tion be­ing marked as closed. This has been fixed.

179060: Con­nec­tion re­cy­cling bug in lo­calTrans­ac­tionMode

Some of the in­con­sis­tent log­ic for non-XA (fixed in 5.0.4) was still around for lo­calTrans­ac­tionMode, caus­ing con­nec­tion re­cy­cling (i.e., reusing the same con­nec­tion in the same thread and trans­ac­tion) to fail. This re­sult­ed in 2 con­nec­tions be­ing used, and 2 par­tic­i­pants for the com­mit (which in turn meant 2-phase com­mit). The net ef­fect: fail­ing pre­pare and no com­mit al­lowed. We've fixed this.

179070: ClassCastEx­cep­tion in non-XA when con­nec­tion in lo­calTrans­ac­tionMode is reused in a JTA trans­ac­tion

There was an ex­cep­tion when try­ing to do the fol­low­ing:

1. Use a non-XA con­nec­tion in lo­calTrans­ac­tionMode, with­out any trans­ac­tion con­text
2. Re­turn the con­nec­tion to the pool for reuse
3. Start a JTA trans­ac­tion
4. Try to reuse the same con­nec­tion from the pool

This was due to re­main­ing state from step 1, caus­ing the last step to fail with a ClassCastEx­cep­tion. This has been fixed.