Let's dive through your stack trace:
--AbstractStore.enlist():
try {
enlisted = transaction.enlistResource(service);
}
catch (Exception e) {
// Something went wrong.
setRollbackOnly();
throw new ServiceAccessException(this, e);
}
--SlideTransaction.enlistResource
try {
xaRes.start(branchXid, flag);
}
catch (XAException e) {
String logMessage = Messages.format
(SlideTransaction.class.getName() + ".enlistFail",
xaRes, getXAErrorCode(e), toString());
transactionManager.getLogger().log(logMessage, LOG_CHANNEL,
Logger.WARNING);
return false;
}
--AbstractRDBMSStore.start
try {
id = new TransactionId(xid, TX_IDLE);
}
catch (SQLException e) {
throw new XAException(XAException.XAER_RMFAIL); // XXX or is it an error?
}
--TransactionId.<init>
connection = getNewConnection();
--J2EEStore.getNewConnection
return ds.getConnection();
So, the problem boils down to the data source throwing SQL exceptions when
asked for new connections. So, as Martin also said, the problem is most
likely a misconfigured data source. Have you tested that data source with
other applications?
-Alejandro
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
