Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 8.0 Update 2
Affects Version/s: 8.0.0.GA
Component/s: JMS
Labels:
None

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/rh-messaging/activemq-artemis/commit/c5f32c664375826565236a24883043dd63dd8dba
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

JBEAP-25595 [GSS](7.4.z) ARTEMIS-4427 - MDB reusing Thread is using wrong transactionTimeout

Verified

is incorporated by

JBEAP-25251 (8.0.z) Upgrade Artemis from 2.21.0.redhat-00045 to 2.21.0.redhat-00048

Resolved

JBEAP-25926 Upgrade AMQ to 7.10.4 (2.21.0.redhat-00045)

Closed

relates to

ENTMQBR-8463 [7.10] MDB reusing Thread is using wrong transactionTimeout

Dev Complete

Assignee:: Emmanuel Hugonnet

Reporter:: Emmanuel Hugonnet

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

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

Updated:: 2024/03/19 8:51 AM

Resolved:: 2024/03/11 3:40 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates

Hide