ExtremeTransactions 4.0.63

Release notes for ExtremeTransactions 4.0.63…

166361: Updated README for REST transactions

Clarified with missing instructions for seamless testing of the demo.

166386: Setting com.atomikos.icatch.max_timeout=0 means unlimited

Improved the new recovery to interpret 0 as unlimited, and we now log a warning if this happens with XA.

166601: Allow delegating JNDI lookups to underlying platform implementation

We've improved our transactions-jndi-provider module: if you use our com.atomikos.jndi.AtomikosContextFactory as the initial context factory then you can delegate unbound lookups to a third-party provider specified as "env."-prefixed properties in the jndi.properties file.

For instance: env.java.naming.factory.initial = … would set the third-party context implementation to delegate to.

166271: LogCloud: conflict between TCC and XA recovery

When deploying the LogCloud there is a conflict between TCC and XA mode - mostly due to timeouts during recovery. We've now made sure that there is better separation to avoid issues with this: either the subsystem starts in XA mode (default) or in TCC mode (if the TCC classes are found on the classpath).

Available to customers only. Want to become a customer?

Send me a quote Message: Please send me a quote for ExtremeTransactions4dot0dot63 Date: 17 Aug 2018 - 03:40 Email: !!address!! Remote-Host: 54.198.126.110