WildFly HornetQ-Based Messaging Subsystem Persistence Configuration

Internal

• Messaging Subsystem Configuration

HornetQ Data Directories

The configuration allows the possibility of creating the HornetQ bindings and journal data directories at startup, if they do not already exist. This configuration could be useful in "experimental" mode when one deletes and recreates HornetQ data files for whatever reason, and probably not that useful in production. If the directories exist, they are not re-created, so the "create" options can be left in place, even in a production configuration. However, there is another set of directories (large messages and paging) that will be created automatically if they don’t exist, in absence of any explicit configuration option. For production, it’s probably best if the directories are created manually as part of the installation procedure, and "create-*" options are removed from configuration.

Message Journal Configuration

For more persistence concepts see:

HornetQ Message Journal Concepts

journal-directory

If the journal lives on a spinning disk, for best performance it should be placed on its own physical volume to minimize head movement.

journal-type

NIO or ASYNCIO

journal-sync-transactional

If true, HornetQ will flush data on disk on transaction boundaries. Default is true.

journal-sync-non-transactional

If true HornetQ will flush non-transactional data on disk (message sends and acknowledgements). Default is true.

Bindings Journal Configuration

For more persistence concepts see:

HornetQ Bindings Journal Concepts

HornetQ JMS Journal Concepts

create-bindings-dir

Specifies whether to create the bindings directory at boot, if it does not already exist. Default is true.

JMS Journal Configuration

See:

Bindings Journal Configuration