Details
-
Bug
-
Resolution: Done
-
Major
-
JBoss A-MQ 6.0
-
None
-
None
Description
Hi,I have a customer trying to use mkahaDB with a master slave configuration:| <mKahaDB directory="../kahadb">|
| <filteredPersistenceAdapters> |
| <!-- kahaDB per destinations --> |
| <filteredKahaDB perDestination="true" > |
| <persistenceAdapter> |
| <kahaDB journalMaxFileLength="32mb" /> |
| </persistenceAdapter> |
| </filteredKahaDB> |
| </filteredPersistenceAdapters> |
I've run into the following issues:1. Starting the slave with an "empty" database, i.e no queues results in the slave trying to start and ultimately failing as the address is in use. There's now lock. Pushing a message to TEST.FOO and then starting the database works OK. The slave comes up and locks and waits.2. Now, adding a TEST.FOO1 to the master. The master now has the two queues, TEST.FOO and TEST.FOO1. Kill the master and let the slave take over. The slave only sees TEST.FOO. Not TEST.FOO1.
