WildFly HornetQ-Based Messaging Subsystem Persistence Configuration: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
 
(16 intermediate revisions by the same user not shown)
Line 2: Line 2:


* [[WildFly HornetQ-Based Messaging Subsystem Configuration#Subjects|Messaging Subsystem Configuration]]
* [[WildFly HornetQ-Based Messaging Subsystem Configuration#Subjects|Messaging Subsystem Configuration]]
* [[HornetQ Persistence Concepts|Persistence Concepts]]
=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=
=Message Journal Configuration=
Line 9: Line 14:
:[[HornetQ Persistence Concepts#Persistent_Message_Journal|HornetQ Message Journal Concepts]]
:[[HornetQ Persistence Concepts#Persistent_Message_Journal|HornetQ Message Journal Concepts]]
</blockquote>
</blockquote>
==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.
==create-journal-dir==
==journal-type==
NIO or ASYNCIO
==journal-sync-transactional==
If <tt>true</tt>, HornetQ will flush data on disk on transaction boundaries. Default is <tt>true</tt>.
==journal-sync-non-transactional==
If <tt>true</tt> HornetQ will flush non-transactional data on disk (message sends and acknowledgements). Default is <tt>true</tt>.
==journal-file-size==
==journal-min-files==
==journal-max-io==
==journal-buffer-timeout==
==journal-buffer-size==
==journal-compact-min-files==
==journal-compact-percentage==


=Bindings Journal Configuration=
=Bindings Journal Configuration=
Line 15: Line 52:
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;">
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;">
:[[HornetQ Persistence Concepts#Bindings_Journal|HornetQ Bindings Journal Concepts]]
:[[HornetQ Persistence Concepts#Bindings_Journal|HornetQ Bindings Journal Concepts]]
:
:[[HornetQ Persistence Concepts#JMS_Journal|HornetQ JMS Journal Concepts]]
</blockquote>
</blockquote>
==bindings-directory==
==create-bindings-dir==
Specifies whether to create the bindings directory at boot, if it does not already exist. Default is <tt>true</tt>.
=JMS Journal Configuration=
See:
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;">
:[[#Bindings_Journal_Configuration|Bindings Journal Configuration]]
</blockquote>
=Large Message Configuration=
==large-message-directory==

Latest revision as of 00:37, 12 March 2016

Internal

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.

create-journal-dir

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.

journal-file-size

journal-min-files

journal-max-io

journal-buffer-timeout

journal-buffer-size

journal-compact-min-files

journal-compact-percentage

Bindings Journal Configuration

For more persistence concepts see:

HornetQ Bindings Journal Concepts
HornetQ JMS Journal Concepts

bindings-directory

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

Large Message Configuration

large-message-directory