-
Bug
-
Resolution: Done
-
Major
-
7.4.z.GA
-
False
-
None
-
False
-
-
-
-
-
-
-
-
-
-
As you can see in https://github.com/wildfly/wildfly-transaction-client/blob/1.1.17.Final/src/main/java/org/wildfly/transaction/client/LocalTransaction.java#L176, the output of setTransactionTimeout is being ignored.
Based on https://docs.oracle.com/javaee%2F6%2Fapi%2F%2F/javax/transaction/xa/XAResource.html#setTransactionTimeout(int), the output of this function determines, whether this function was successful.
the transaction client do log that the setTransactionTimeout was not successful in case of exception being thrown, but not in case of false returned
- causes
-
WFTC-142 Lower logging level to debug for transaction timeout
- Resolved
-
JBEAP-26686 (7.4.z) WFTC-142 - Lower logging level to debug for transaction timeout
- Closed
- is cloned by
-
WFTC-141 Wildfly-transaction-client doesn't log that the transaction timeout wasn't set, when the driver returns false.
- Resolved
-
JBEAP-26364 (8.0.z) WFTC-141 - Wildfly-transaction-client doesn't log that the transaction timeout wasn't set, when the driver returns false.
- Closed
- is incorporated by
-
JBEAP-26406 (7.4.z) Upgrade wildfly-transaction-client from 1.1.17.Final-redhat-00001 to 1.1.19.Final-redhat-00001
- Closed
- relates to
-
JBEAP-26361 Network failure in prepare phase can cause a permanent table lock-out on Sybase
- New