Red Hat Summit Red Hat SummitSupportKonsoleEntwicklerDemo startenKontakt

Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.

36.5.2. Specifying a Static Cluster Server List

It is possible to define a symmetric cluster and not use static server discovery so each node can in turn discover available nodes. Configuring each cluster connection to have explicit knowledge of all the other nodes in the cluster is required.

Important

Fail-over is not supported for clusters defined using a static cluster server list. To support fail-over between cluster nodes, the nodes must be configured to use a discovery group.

Task: Specify Cluster Server List without Auto Discovery

Complete this task to specify a static cluster server list instead of using server auto discovery.

Prerequisites

  • The <JBOSS_HOME>/jboss-as/server/<PROFILE>/deploy/hornetq/hornetq-configuration.xml file open, ready to add directives.
  • Understand the hornetq-configuration.xml configuration directives, as detailed in Section A.1.1, “hornetq-configuration.xml”.

  1. Define Connectors

    In the hornetq-configuraton.xml file, insert a <connectors> directive block defining the remoting connector factory, the names of connectors, and the ports each connector will use.
    Each connector must use a unique port. 
    <connectors>
  <connector name="netty-connector">
    <factory-class>
     org.hornetq.core.remoting.impl.netty.NettyConnectorFactory
    </factory-class>
  <param key="port" value="5445"/>
</connector>
<!-- connector to the server1 -->
  <connector name="server1-connector">
    <factory-class>
     org.hornetq.core.remoting.impl.netty.NettyConnectorFactory
    </factory-class>
    <param key="port" value="5446"/>
  </connector>
<!-- connector to the server2 -->
  <connector name="server2-connector">
    <factory-class>
     org.hornetq.core.remoting.impl.netty.NettyConnectorFactory
    </factory-class>
    <param key="port" value="5447"/>
  </connector>
</connectors>
    Copy to Clipboard Toggle word wrap

  2. Define Cluster Connection

    Insert a <cluster-connection> directive block. The block must contain mandatory clustering directives, and the <connector-ref> directives set in the previous step. The <connector-ref> directives use the name attribute set in the <connector> directives. 
    <cluster-connections>
  <cluster-connection name="my-cluster">
    <address>jms</address>
    <connector-ref>netty-connector</connector-ref>
    <retry-interval>500</retry-interval>
    <use-duplicate-detection>true</use-duplicate-detection>
    <forward-when-no-consumers>true</forward-when-no-consumers>
    <max-hops>1</max-hops>
    <static-connectors>
      <connector-ref>server1-connector</connector-ref>
      <connector-ref>server2-connector</connector-ref>
    </static-connectors>
  </cluster-connection>
</cluster-connections>
    Copy to Clipboard Toggle word wrap

  3. Result

    The cluster is now defined with the directives required for server discovery using explicit server names.
Nach oben
Red Hat logoGithubredditYoutubeTwitter

Lernen

Testen, kaufen und verkaufen

Communitys

Über Red Hat Dokumentation

Wir helfen Red Hat Benutzern, mit unseren Produkten und Diensten innovativ zu sein und ihre Ziele zu erreichen – mit Inhalten, denen sie vertrauen können. Entdecken Sie unsere neuesten Updates.

Mehr Inklusion in Open Source

Red Hat hat sich verpflichtet, problematische Sprache in unserem Code, unserer Dokumentation und unseren Web-Eigenschaften zu ersetzen. Weitere Einzelheiten finden Sie in Red Hat Blog.

Über Red Hat

Wir liefern gehärtete Lösungen, die es Unternehmen leichter machen, plattform- und umgebungsübergreifend zu arbeiten, vom zentralen Rechenzentrum bis zum Netzwerkrand.

Theme

© 2025 Red Hat