HornetQ Persistence Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
==Persistent Messages== | ==Persistent Messages== | ||
All persistent messages ''must'' be stored on persistent storage, as mandated by the JMS specification. This is necessary to protect against messaging system failure: a persistent message can be presumably recovered from the persistent storage and re-sent. | |||
==Bindings== | ==Bindings== | ||
Revision as of 21:44, 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?
Persistent Messages
All persistent messages must be stored on persistent storage, as mandated by the JMS specification. This is necessary to protect against messaging system failure: a persistent message can be presumably recovered from the persistent storage and re-sent.
Bindings
JMS
Large Messages
Non Persistent Messages
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.