This is how we are considering implementing multiple message stores (currently we are only looking at doing this for the KahaDB store):
1. Provide a new implementation of PersistenceAdapter, called KahaDBMultiStorePersistenceAdapter that can be configured in the activemq.xml file. This would contain multiple instances of KahaDBStore, and would also store the mapping from destination name to KahaDBStore instance (configured in persistence adapter element in the xml). We are not looking at configuring this mapping using destination policies at the moment, as this looks like it would require more substantial code changes that we don't currently have time to implement. 2. Modify the MessageDatabase class, to allow the filenames used for the page and lock files to be configurable. These would default to the harcoded names that are currently used. We would have one set of page and lock files per KahaDBStore instance. We feel that this allows us to add the functionality we require, while having a minimal impact on the existing code. Does this seem reasonable? Thanks, Pete. -- View this message in context: http://activemq.2283324.n4.nabble.com/KahaDB-log-f-tp2539334p2547115.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
