Major With a per-destination configuration for mKahadb, (empty) topic kahadbs are not removed. With a high number of topics, the startup time of A-MQ is impacted. The business use case requires that each destination have a separate kahadb.
Allow empty destinations for per-destination mkahadbs to be removed on A-MQ restart
-
Gary Tully
-
Stephen Higgs
- Votes:
-
0 Vote for this issue
- Watchers:
-
4 Start watching this issue
- Created:
- Updated:
- Resolved: