Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 7.4.14.CR1, 7.4.14.GA
Affects Version/s: None
Component/s: JMS
Labels:
- upstream-linked

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/rh-messaging/activemq-artemis/commit/5a86c4c50d3435d7e9913930df9ac24aab4ba7ab
Intelligence Requested:
Market:

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

The wrong transactionTimeout being used by a MDB (that does not set an explict transactionTimeout) in case it runs on a Thread where previously another MDB with an explicitly set transactionTimetout was running.

Attached you find the playground.tar.gz that is reproducing the observed behaviour. This project contains a README.txt that explains the project and the observed behaviour in more detail.

clones

WFLY-18433 MDB reusing Thread is using wrong transactionTimeout

Closed

is cloned by

JBEAP-25596 [GSS](8.0.z) ENTMQBR-8367 - MDB reusing Thread is using wrong transactionTimeout

Closed

is incorporated by

JBEAP-25657 (7.4.z) Upgrade Artemis from 2.16.0.redhat-00049 to 2.16.0.redhat-00051

Closed

relates to

ENTMQBR-8462 [7.8.EAP] MDB reusing Thread is using wrong transactionTimeout

Closed

ENTMQBR-8464 Productize AMQ Broker 7.8 build for EAP 7.4.14

Closed

Assignee:: Emmanuel Hugonnet

Reporter:: Emmanuel Hugonnet

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 2023/09/12 2:02 PM

Updated:: 2024/08/19 2:02 PM

Resolved:: 2023/10/18 6:39 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates