-
Bug
-
Resolution: Done
-
Major
-
8.0.0.GA
-
None
-
False
-
None
-
False
-
-
-
-
-
-
+
-
Known Issue
-
-
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
- Closed
- is incorporated by
-
JBEAP-25926 Upgrade AMQ to 7.10.4 (2.21.0.redhat-00045)
- Closed
-
JBEAP-25251 (8.0.z) Upgrade Artemis from 2.21.0.redhat-00045 to 2.21.0.redhat-00048
- Closed
- relates to
-
ENTMQBR-8463 [7.10] MDB reusing Thread is using wrong transactionTimeout
- Dev Complete