WildFly HornetQ-Based Messaging Subsystem Concepts

From NovaOrdis Knowledge Base
Revision as of 03:16, 28 February 2016 by Ovidiu (talk | contribs) (→‎Clustering)
Jump to navigation Jump to search

External

Internal

Connector

Acceptor

Address

Persistence

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.

Journal

Broadcast Group

Discovery Group

Clustering

Clustering in this context means establishing a mesh of HornetQ brokers. The main purpose of creating a cluster is to spread message processing load across more than one node. Each active node in the cluster acts as an independent HornetQ server and manages its own connections and messages.

High Availability

https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.3/html/Administration_and_Configuration_Guide/sect-High_Availability.html

Dedicated Topology

Collocated Topology

Retrieved from "https://kb.novaordis.com/index.php?title=WildFly_HornetQ-Based_Messaging_Subsystem_Concepts&oldid=4123"