Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 7.4.17.CR1, 7.4.17.GA
Affects Version/s: None
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:
Target Release:

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

SFDC Cases Counter:
SFDC Cases Links:

https://issues.redhat.com/browse/WFTC-141 introduced logging of transaction timeout at the warning level. This causes warning for every transaction for EAP customers, which they haven't encountered before and even when using correct configuration. This should be lowered to DEBUG

blocks

JBEAP-26406 (7.4.z) Upgrade wildfly-transaction-client from 1.1.17.Final-redhat-00001 to 1.1.19.Final-redhat-00001

Ready for QA

clones

WFTC-142 Lower logging level to debug for transaction timeout

Resolved

is caused by

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-26406 (7.4.z) Upgrade wildfly-transaction-client from 1.1.17.Final-redhat-00001 to 1.1.19.Final-redhat-00001

Ready for QA

relates to

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.

Resolved

Assignee:: Petr Beran

Reporter:: Petr Beran

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2024/02/22 8:58 AM

Updated:: 2024/04/25 12:42 PM

Resolved:: 2024/02/26 9:31 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates