Chapter 8. Message Store Lockers
Abstract
Message store locks are used to elect the master broker in master/slave groups. They are also useful for ensuring that multiple brokers are not attempting to share the same message store. Red Hat JBoss A-MQ's lockers are configurable to allow for tuning.
8.1. Locker Basics
Overview
Red Hat JBoss A-MQ provides two default lockers that are used based on the type of message store being used:
- shared file locker—used by KahaDB and LevelDB stores
- database locker—used by the JDBC storeNoteJBoss A-MQ also provides a leased database locker that can be in cases where the brokers may periodically lose their connection to the message store.
These default lockers are configurable to optimize their performance.
For further optimization, you can implement your own locker and plug it into the message store. Doing so involves implementing a simple Java interface and adding some configuration to the persistence adapter.
Message store locks are primarily leveraged by the broker for electing masters in master/slave configurations. For more information on master/slave groups see chapter "Master/Slave" in "Fault Tolerant Messaging".
Configuring a persistence adapter's locker
To configure the locker used by a persistence adapter you add a
locker element as a child to the adapter's configuration element as shown in Example 8.1, “Configuring a Message Store Locker”.
Example 8.1. Configuring a Message Store Locker
<persistenceAdapter>
<kahaDB directory = "target/activemq-data">
<locker>
...
</locker>
</kahaDB>
</persistenceAdapter>Standard locker configuration properties
All locker implementations are required to have the two common configuration properties described in Table 8.1, “Common Locker Properties”.
The properties are specified as attributes to the locker's XML configuration element.
