-
Bug
-
Resolution: Done
-
Major
-
None
set-tx-query-timeout feature depends on org.jboss.tm.TransactionTimeoutConfiguration#getTimeLeftBeforeTransactionTimeout() to get the remaining time of transaction timeout from transaction manager.
org.jboss.as.connector.services.transaction.integration.TransactionIntegrationServer passes transaction manager instance to org.jboss.jca.core.tx.jbossts.TransactionIntegrationImpl. The transaction manager instance is different between EAP 7.0.x and EAP 7.1.0 (IIUC, this change happened because of Elytron integration):
- In EAP 7.0.x, the instance is com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate which implements org.jboss.tm.TransactionTimeoutConfiguration.
- In EAP 7.1.0, the instance is org.wildfly.transaction.client.ContextTransactionManager which does not implement org.jboss.tm.TransactionTimeoutConfiguration.
Therefore, set-tx-query-timeout feature does not work in EAP 7.1.0.
To fix this issue, I think org.wildfly.transaction.client.ContextTransactionManager needs to implement org.jboss.tm.TransactionTimeoutConfiguratio#getTimeLeftBeforeTransactionTimeout()
- clones
-
WFLY-10674 set-tx-query-timeout does not work at all because ContextTransactionManager does not implement TransactionTimeoutConfiguration#getTimeLeftBeforeTransactionTimeout()
- Closed
- is caused by
-
JBJCA-1378 Use new API to determine remaining transaction timeout
- Resolved
- is cloned by
-
JBEAP-13775 [GSS](7.1.z) set-tx-query-timeout does not work at all because ContextTransactionManager does not implement TransactionTimeoutConfiguration#getTimeLeftBeforeTransactionTimeout()
- Closed
- is incorporated by
-
WFLY-10675 Upgrade to ironjacamar 1.4.11 Final
- Closed
- is related to
-
JBEAP-15349 (7.2.z) NoClassDefFoundError when set-tx-query-timeout is enabled (followup to JBJCA-1378)
- Closed
- links to