I have a GlassFish server that is set up to use NON-XA data sources in its
connection pools.
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:
com.sun.appserv.connectors.internal.api.PoolingException:
javax.resource.spi.LocalTransactionException: Connection not established
at
com.sun.enterprise.resource.ConnectorXAResource.handleResourceException(ConnectorXAResource.java:115)
at
com.sun.enterprise.resource.ConnectorXAResource.start(ConnectorXAResource.java:150)
at
com.sun.enterprise.transaction.JavaEETransactionManagerSimplified.enlistResource(JavaEETransactionManagerSimplified.java:378)
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.
Thanks,
Laird
--
http://about.me/lairdnelson