Show Table of Contents
20.14.5. Configuring HornetQ for Dedicated Topology with Shared Store
To configure the live and backup servers for shared store in dedicated topology, configure the
The backup server must also be flagged explicitly as a backup.
standalone-X.xml files on each server to have the following:
<shared-store>true</shared-store>
<paging-directory path="${shared.directory}/journal"/>
<bindings-directory path="${shared.directory}/bindings"/>
<journal-directory path="${shared.directory}/journal"/>
<large-messages-directory path="${shared.directory}/large-messages"/>
.
.
.
<cluster-connections>
<cluster-connection name="my-cluster">
...
</cluster-connection>
</cluster-connections>
Table 20.14. HornetQ Servers Setup Attributes (for both live and backup servers)
| Attribute | Description |
|---|---|
| shared-store |
Whether this server is using shared store or not. Default is false
|
| paging-directory path |
This indicates the path to the paging directory. This path is the same for both live and backup servers as they share this directory
|
| bindings-directory path |
This indicates the path to the binding journal. This path is the same for both live and backup servers as they share this journal
|
| journal-directory path |
This indicates the path to the journal directory. This path is the same for both live and backup servers as they share this directory
|
| large-messages-directory path |
This indicates the path to the large messages directory. This path is the same for both live and backup servers as they share this directory
|
| failover-on-shutdown |
Whether this server becomes active when live or currently active backup server shuts down
|
<backup>true</backup>The setup attribute exclusively for HornetQ backup server is:
allow-failback. This specifies whether the backup server will automatically shutdown if the original live server comes back up.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.