-
Bug
-
Resolution: Done
-
Major
-
JBoss A-MQ 6.1
-
None
-
- Run the attached test case.
Hey guys, had a customer run into stuck messages on their broker when using the attached configuration. Currently, their QA environment is using Oracle, but we were able to reproduce the issue in MySQL. I was able to see the behavior on my end as well. I've attached the test case used to recreate this issue, as well as the logs taken when this issue occurred.
Restarting the broker appears to solve the issue. Case seems similar to https://issues.jboss.org/browse/ENTMQ-538, however this takes place in a single broker
- causes
-
ENTMQ-1791 Regression in from ENTMQ-703 leads to metrics issue for temp transactional queues
- Closed
- incorporates
-
ENTMQ-692 Issues with concurrentStoreAndDispatchQueue
- Closed
- relates to
-
ENTMQ-805 Performance degradation when running test case from https://issues.jboss.org/browse/ENTMQ-703 with KahaDB
- Closed