-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
From https://issues.apache.org/jira/browse/AMQ-4480Using the following mKahaDB config:| <persistenceAdapter>|
| <mKahaDBdirectory="${activemq.data}/kahadb"> |
| <filteredPersistenceAdapters> |
| <filteredKahaDBperDestination="true"> |
| <persistenceAdapter> |
| <kahaDBjournalMaxFileLength="32mb"/> |
| </persistenceAdapter> |
| </filteredKahaDB> |
| </filteredPersistenceAdapters> |
| </mKahaDB> |
| </persistenceAdapter> |
Note perDestination="true".
Using that configuration and sending a message to a JMS queue whose name is longer than 50 characters, this destination's messages won't be loaded eagerly upon a restart of the broker. As a result that destination does not show up in JMX.Only when a producer or consumer connects to this destination, this destination gets loaded from kahadb as this broker log output confirms| INFO | KahaDB is version 4|
| INFO | Recovering from the journal ... |
| INFO | Recovery replayed 1 operations from the journal in 0.0010 seconds. |
This log output is written after the broker had completely started up.