Loading...

XML

Word

Printable

Steps to Reproduce:

Hide

Test cases available on internal trackers

Show
Test cases available on internal trackers

We have a few issues that have identified problems with concurrentStoreAndDispatchQueue namely messages get stuck in a network of brokers.

To avoid this issue we've disabled the setting:
concurrentStoreAndDispatchQueue=false

and also set

expireMessagesPeriod=0

is incorporated by

ENTMQ-703 Stuck Messages in Single Broker when using JDBC Persistent Store

is related to

ENTMQ-282 Un-browsable messages in broker mesh with large volume of data

ENTMQ-444 Stuck messages in a network of brokers that don't get dispatched to consumer

ENTMQ-687 Duplicate messages are created for KahaDB and performance of Camel route from one queue to another is lower in LevelDB than in KahaDB

relates to

ENTMQ-744 Network of Brokers Stops Dispatching Messages