Configuring a Remote HornetQ JMS Server as a Resource Adapter
Jump to navigation
Jump to search
External
Internal
Overview
This article describes the configuration required to make a cluster of two HornetQ-based JMS nodes, running as messaging subsystems within EAP 6.4 instances, accessible to a third JBoss EAP 6.4. The cluster will be deployed as resource adapter within the third JBoss instance, and thus available to the MDBs deployed on that JBoss instance.
The procedure consists in declaring netty connections from the resource adapter node to the HornetQ nodes and using those connections from a pooled connection which exposes the remote cluster as a resource adapter.
Procedure
Declare the Outbound Socket Bindings
<outbound-socket-binding name="remote-hornetq-node-1"> <remote-destination host="${remote.hornetq.node.1.address:127.0.0.1}" port="${remote.hornetq.node.1.port:5545}"/> </outbound-socket-binding> <outbound-socket-binding name="remote-hornetq-node-2"> <remote-destination host="${remote.hornetq.node.2.address:127.0.0.1}" port="${remote.hornetq.node.2.port:5645}"/> </outbound-socket-binding>
Note that the above configuration implies that the HornetQ node 1 runs with a port offset of 100, and HornetQ node 2 runs with a port offset of 200.