XA transaction errors on non-XA connection pools?
I have a GlassFish server that is set up to use NON-XA data sources in its
The log for that domain (yes, that domain, no, I'm not mixing up domains
but good question :-)) contains various XA errors. Here's a short snippet:
Caused by: javax.transaction.xa.XAException:
javax.resource.spi.LocalTransactionException: Connection not established
Given that XA is nowhere in evidence, I was wondering if there is some way
that GlassFish could be starting XA transactions anyway? At sea here.