This content has been marked as final. Show 3 replies
I wonder why do you use own TransactionTimeoutConfiguration class (org.jboss.jca.core.spi.transaction.TransactionTimeoutConfiguration) when having org.jboss.tm.TransactionTimeoutConfiguration? It seems to cause a bug:
in org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl#getTimeLeftBeforeTransactionTimeout you check if transactionManager is instance of org.jboss.jca.core.spi.transaction.TransactionTimeoutConfiguration, but transactionManager comes from jbosstm, it is instance of com.arjuna.ats.jbossatx.jts.TransactionManagerDelegate in my case, that in turn implements org.jboss.tm.TransactionTimeoutConfiguration. So check always fails.
Is that a bug or misconfiguration? Should I post an issue to JIRA?
Thank you in advance.