6 Replies Latest reply on Jan 23, 2011 11:40 AM by edward_bai

    AS 6.0.0.M4 clustering on single machine

    lubu21

      Hi, i'm trying to set up a jboss AS cluster on my machine by running 2 instances first with

       

      run -c all

       

      and another with

       

      run -c all2 -Djboss.service.binding.set=ports-01 -Djboss.messaging.ServerPeerID=1

       

      After both of them are started, i get this message getting flooded in my console

       

      2010-08-12 09:54:59,446 WARN  [org.hornetq.core.cluster.impl.DiscoveryGroupImpl] (hornetq-discovery-group-thread-dg-group1) There are more than one servers on the network broadcasting the same node id. You will see this message exactly once (per node) if a node is restarted, in which case it can be safely ignored. But if it is logged continuously it means you really do have more than one node on the same network active concurrently with the same node id. This could occur if you have a backup node active at the same time as its live node.

       

      Am kinda new in these stuff, what have i done wrong or missed out...?

      Any help will be appreciated =]

        • 1. Re: AS 6.0.0.M4 clustering on single machine
          jaikiran

          Yong Hon Cheong wrote:

           


           

          2010-08-12 09:54:59,446 WARN  [org.hornetq.core.cluster.impl.DiscoveryGroupImpl] (hornetq-discovery-group-thread-dg-group1) There are more than one servers on the network broadcasting the same node id. You will see this message exactly once (per node) if a node is restarted, in which case it can be safely ignored. But if it is logged continuously it means you really do have more than one node on the same network active concurrently with the same node id. This could occur if you have a backup node active at the same time as its live node.

           


          This log message looks a bit specific to HornetQ. I'll move this thread there. Someone there might be able to answer.

          • 2. Re: AS 6.0.0.M4 clustering on single machine
            lubu21

            Ok please do, im not even sure where should i post this, thanks for the help moving it to the right place

            • 3. AS 6.0.0.M4 clustering on single machine
              edward_bai

              The same question on jboss-6.0.0.Final.

              • 4. AS 6.0.0.M4 clustering on single machine
                kevin-ncsu

                I had this same issue earlier today.  You likely copied the entire "all" server directory after you had already started it once which causes the data directory to be copied over as well.  This causes both nodes to start up with the same server ID sa HornetQ saves it's bindings there.  If you don't have anything in the data directory you need (ie. you can go back to a fresh config) I solved this by deleting the data directory for both nodes. 

                 

                Well, I actually deleted the data, log, and tmp and work directories to make absolutely sure I had a fresh setup, but I'm pretty sure it's only the data one you need to worry about.

                • 5. AS 6.0.0.M4 clustering on single machine
                  clebert.suconic

                  You probably copied the journal files between two different nodes.

                   

                  The serverID is now dynamically generated, with an UUID at the first time the server is started. (I mean with an empty journal)

                   

                   

                  if you started the server, then cloned the server, the same UUID will be applied to the cloned server and hence you will start to see errors.

                   

                  You should probably cleanup the data files.

                  • 6. AS 6.0.0.M4 clustering on single machine
                    edward_bai

                    Thank you, Clebert. It works right now.