7 Replies Latest reply on Nov 13, 2012 9:16 AM by Anas Rabei

    Jboss Messaging Clustering Strange behaviore

    Anas Rabei Newbie

      I am trying to get a cluster of two jboss nodes working but I met some strange behavior

       

      First of all here is how I installed the two nodes.

       

      The two nodes working in standalone mode with the configuration standalone-full-ha.xml.

       

      Here is the changes I have made in the two configuration files.

       

      1- the interfaces section -> I have changed the IPs in the two files from 127.0.0.1 to the machine IPs

      the first file

      ----------------

      <interfaces>

              <interface name="management">

                  <inet-address value="${jboss.bind.address.management:193.16.1.67}"/>

              </interface>

              <interface name="public">

                  <inet-address value="${jboss.bind.address:193.16.1.67}"/>

              </interface>

              <!-- TODO - only show this if the jacorb subsystem is added  -->

              <interface name="unsecure">

                  <!--

                    ~  Used for IIOP sockets in the standard configuration.

                    ~                  To secure JacORB you need to setup SSL

                    -->

                  <inet-address value="${jboss.bind.address.unsecure:193.16.1.67}"/>

              </interface>

          </interfaces>

       

       

      the second file

      ---------------------

      <interfaces>

              <interface name="management">

                  <inet-address value="${jboss.bind.address.management:193.16.1.93}"/>

              </interface>

              <interface name="public">

                  <inet-address value="${jboss.bind.address:193.16.1.93}"/>

              </interface>

              <!-- TODO - only show this if the jacorb subsystem is added  -->

              <interface name="unsecure">

                  <!--

                    ~  Used for IIOP sockets in the standard configuration.

                    ~                  To secure JacORB you need to setup SSL

                    -->

                  <inet-address value="${jboss.bind.address.unsecure:193.16.1.93}"/>

              </interface>

          </interfaces>

       

      2- For nodes to discover esch others I am using TCP instead of UDP and here is the configuration in the two files

      <subsystem xmlns="urn:jboss:domain:jgroups:1.1" default-stack="tcp">

                  <stack name="udp">

                      ................

                  </stack>

                  <stack name="tcp">

                      <transport type="TCP" socket-binding="jgroups-tcp" diagnostics-socket-binding="jgroups-diagnostics"/>

                          <protocol type="TCPPING">

                          <property name="initial_hosts">193.16.1.67[7600],193.16.1.93[7600]</property>

                          <property name="num_initial_members">2</property>

                          <property name="port_range">0</property>

                          <property name="timeout">2000</property>

                      </protocol>

                      ...................

                  </stack>

              </subsystem>

       

      Now here is the problems I am facing and can not understand what is the wrong with my installation

       

      1- I have developed a little java application that send messages to the first machine (193.16.1.93) and tries to consume the message from the other machine (193.16.1.67) and this works perfectly but when I try to revers the IPs (send to 193.16.1.67 and consum from 193.16.1.93) the sender works fine but the messages does not delivered to the machine 193.16.1.93 (the message return is null) which indicates that the messages is not sent from machine 67 to machine 93 -while the reverts scenario works fine-. what would be the problem here?

       

      2- When restaring jboss on the machine 67, I got a warnning message in the losg of the other node that (there is another node in the same network broadcast the same node id). I understand that this is a normal warnning message in case of node restart and I am assuming that if I reversed the process (restart node 93 and check node 67 logs) the same warnning will appeare in the node 67 log but this does not happend. Also, what would be the problem here ?

       

      3- Node 67 frequently throws the exception Faild To create netty connection SocketTimeOutException.

       

      I am using Jboss 7.1.1-final and the code of the application I use to send and consume the message is attached

       

      I hope getting any help here

       

      Message was edited by: Anas Rabei