0 Replies Latest reply on May 15, 2012 10:32 AM by SMS JBOSS

    JBOSS AS 7.1 HornetQ cluster problem (Netty Connector Problem)

    SMS JBOSS Newbie

      Below is the cluster configuration in the server 1. In the server 2, we have updated the <cluster-password> and the connector host ip address.

       

                      <clustered>true</clustered>

                      <persistence-enabled>true</persistence-enabled>

                      <cluster-password>myClusterPassword</cluster-password>

                      <journal-file-size>102400</journal-file-size>

                      <journal-min-files>2</journal-min-files>

       

       

                      <connectors>

                          <connector name="server1-connector">

                              <factory-class>org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</factory-class>

                              <param key="host" value="20.0.12.111"/>

                              <param key="port" value="5445"/>

                          </connector>

                          <netty-connector name="netty" socket-binding="messaging"/>

                          <netty-connector name="netty-throughput" socket-binding="messaging-throughput">

                              <param key="batch-delay" value="50"/>

                          </netty-connector>

                          <in-vm-connector name="in-vm" server-id="0"/>

                      </connectors>

       

       

                      <acceptors>

                          <acceptor name="server1-connector">

                              <factory-class>org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory</factory-class>

                              <param key="host" value="0.0.0.0"/>

                              <param key="port" value="5445"/>

                          </acceptor>

                          <netty-acceptor name="netty" socket-binding="messaging"/>

                          <netty-acceptor name="netty-throughput" socket-binding="messaging-throughput">

                              <param key="batch-delay" value="50"/>

                              <param key="direct-deliver" value="false"/>

                          </netty-acceptor>

                          <in-vm-acceptor name="in-vm" server-id="0"/>

                      </acceptors>

       

       

                      <cluster-connections>

                          <cluster-connection name="my-cluster">

                              <address>#</address>

                              <connector-ref>netty</connector-ref>

                              <forward-when-no-consumers>true</forward-when-no-consumers>

                              <static-connectors>

                                  <connector-ref>

                                      server1-connector

                                  </connector-ref>

                              </static-connectors>

                          </cluster-connection>

                      </cluster-connections>

       

      In the server1 , the console says, Cluster connection is Connected. But in the Server2, it says cluster is connected and immediately it says "Failed to create netty connection".

       

      (1) Can anyone say why is this happening.

       

      (2) Is there a way I can specify the  connector ip address to which the cluster needs to be formed during the start of the server, something like a server start time parameter.

      "<param key="host" value="20.0.12.111"/>"

       

      19:34:46,882 INFO  [org.hornetq.core.server.cluster.impl.BridgeImpl] (Thread-13 (HornetQ-server-HornetQServerImpl::serverUUID=1170bbf2-9803-11e1-ab57-c8bcc892ab04-146780063)) Bridge ClusterConnectionBridge@3b1674f0 [name=sf.my-cluster.e420bcd5-8d31-11e1-8c61-00250045e8c4, queue=QueueImpl[name=sf.my-cluster.e420bcd5-8d31-11e1-8c61-00250045e8c4, postOffice=PostOfficeImpl [server=HornetQServerImpl::serverUUID=1170bbf2-9803-11e1-ab57-c8bcc892ab04]]@3f5756de targetConnector=ServerLocatorImpl (identityfrown.tifCluster-connection-bridge::ClusterConnectionBridge@3b1674f0 [name=sf.my-cluster.e420bcd5-8d31-11e1-8c61-00250045e8c4, queue=QueueImpl[name=sf.my-cluster.e420bcd5-8d31-11e1-8c61-00250045e8c4, postOffice=PostOfficeImpl [server=HornetQServerImpl::serverUUID=1170bbf2-9803-11e1-ab57-c8bcc892ab04]]@3f5756de targetConnector=ServerLocatorImpl [initialConnectorsembarrassed.tiforg-hornetq-core-remoting-impl-netty-NettyConnectorFactory?port=5445&host=localhost], discoveryGroupConfiguration=null]]::ClusterConnectionImpl@263990790[nodeUUID=1170bbf2-9803-11e1-ab57-c8bcc892ab04, connector=org-hornetq-core-remoting-impl-netty-NettyConnectorFactory?port=5445&host=localhost, address=#, server=HornetQServerImpl::serverUUID=1170bbf2-9803-11e1-ab57-c8bcc892ab04])) [initialConnectorsembarrassed.tiforg-hornetq-core-remoting-impl-netty-NettyConnectorFactory?port=5445&host=localhost], discoveryGroupConfiguration=null]] is connected

       

       

      19:34:53,284 ERROR [org.hornetq.core.remoting.impl.netty.NettyConnector] (Thread-8 (HornetQ-server-HornetQServerImpl::serverUUID=1170bbf2-9803-11e1-ab57-c8bcc892ab04-146780063)) Failed to create netty connection: java.net.SocketTimeoutException: connect timed out