Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 8.0 Update 2
Affects Version/s: 8.0.0.GA-CR2
Component/s: Transactions
Labels:
- regression_test_only

Blocked:
False
Blocked Reason:
None
Ready:
False
CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
QE Test Coverage:
-
Release Note Type:
Known Issue
Target Release:

8.0.z.GA
Git Pull Request:
https://github.com/wildfly/wildfly-transaction-client/pull/196
Intelligence Requested:
Market:

SFDC Cases Counter:
SFDC Cases Links:

As you can see in https://github.com/wildfly/wildfly-transaction-client/blob/main/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

clones

JBEAP-26363 (7.4.z) WFTC-141 - Wildfly-transaction-client doesn't log that the transaction timeout wasn't set, when the driver returns false.

Ready for QA

is incorporated by

JBEAP-26407 (8.0.z) Upgrade wildfly-transaction-client from 3.0.2.Final-redhat-00001 to 3.0.5.Final-redhat-00001

Resolved

is related to

JBEAP-26686 (7.4.z) WFTC-142 - Lower logging level to debug for transaction timeout

Ready for QA

relates to

JBEAP-26362 Network failure in prepare phase can cause a permanent table lock-out on Sybase

New

Assignee:: Lukas Vydra

Reporter:: Ondrej Gerzicak

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 2024/01/09 10:29 AM

Updated:: 2024/03/14 8:49 AM

Resolved:: 2024/03/07 8:54 PM