HornetQ Persistence Concepts: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
=Overview= | =Overview= | ||
Disk only. | |||
HornetQ does not support database-based persistence. For reasons that went into this decision see https://developer.jboss.org/thread/153581. More details in "Messaging persistence in EAP 6.x" https://access.redhat.com/solutions/226743. | HornetQ does not support database-based persistence. For reasons that went into this decision see https://developer.jboss.org/thread/153581. More details in "Messaging persistence in EAP 6.x" https://access.redhat.com/solutions/226743. | ||
=What Does HornetQ Persist?= | |||
=Journal= | =Journal= | ||
When a node is started for the first time it persists a unique identifier into its journal directory. This ID is needed for proper formation of [[#Clustering|clusters]]. | When a node is started for the first time it persists a unique identifier into its journal directory. This ID is needed for proper formation of [[#Clustering|clusters]]. | ||
Revision as of 21:38, 11 March 2016
Internal
Overview
Disk only.
HornetQ does not support database-based persistence. For reasons that went into this decision see https://developer.jboss.org/thread/153581. More details in "Messaging persistence in EAP 6.x" https://access.redhat.com/solutions/226743.
What Does HornetQ Persist?
Journal
When a node is started for the first time it persists a unique identifier into its journal directory. This ID is needed for proper formation of clusters.