Ex­tremeTrans­ac­tions 4.0.62

166145: LogCloudRmiServ­er: lookup re­cov­ery de­lay in con­fig prop­er­ties

This class used to take a sep­a­rate pa­ra­me­ter on the com­mand line - there­by hid­ing the val­ue spec­i­fied in the jta.prop­er­ties file. This has been fixed.

166164: Bug in ACID/REST demo

Fixed a bug in the demo: the in­ven­to­ry should not re­turn "Ac­cept­ed" sta­tus for up­dates.

166167: ACID/REST: added client-side checks to pre­vent com­mit when there are out­stand­ing re­mote calls

It should not be al­lowed to have a com­mit when some calls are still pend­ing - since the com­mit scope will not be well-de­fined in that case. We now have a check for that.

166171: Trans­ac­tionAwareRestCon­tain­erFil­ter: time­out must be rel­a­tive to Sys­tem time

Fixed a bug where the time­out was con­fused with the ex­pi­ra­tion date/time in the re­quest head­er of in­com­ing re­quests. This would lead to ex­ces­sive time­outs.

166211: ACID/REST: con­tain­er (serv­er-side) fil­ter should not add par­tic­i­pant head­er on roll­back

For ex­tra safe­ty, we've im­proved the fil­ter to omit any head­ers in case of serv­er-side roll­back. This way, the client trans­ac­tion man­ag­er can­not get con­fused and still at­tempt com­mit.

166212: ACID/REST: client fil­ter should roll­back if trans­ac­tion was prop­a­gat­ed but no par­tic­i­pant link head­er re­turned

Be­cause of the pre­vi­ous case (166211), the client should not com­mit a trans­ac­tion where there is no par­tic­i­pant for the re­mote work. Other­wise, the trans­ac­tion com­mit scope would be un­de­fined.

165415: ACID/REST: al­low ex­port­ing any lo­cal JTA trans­ac­tion

We've im­proved the ex­am­ples and added sup­port for both JAX-RS and Spring REST/MVC - so you can build mi­croser­vices with your favourite tool­box.

165427: ACID/REST: add log­ging so we can see what hap­pens

We've im­proved log­ging in the REST mod­ule - so it's eas­i­er to see what hap­pens.

165799: New data­source prop­er­ty con­cur­ren­tCon­nec­tionVal­i­da­tion: also log on init

It seems we did not log this new prop­er­ty val­ue on init yet. This has now been fixed.

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