4 Replies Latest reply on May 15, 2006 5:37 PM by damo9f

    Clustering and UDP traffic (and errors) in non-clustered env

      We found that our version of JBoss (4.0.3 sp1) was configured for clustering out-of-the box and have been unable to disable all clustering traffic since this dicovery.

      We removed tc5-cluster.xml and cluster-service.xml but have still not been able to supress various UDP multicast messages, and messages such as

      [TreeCache] viewAccepted(): new members: [blast:1029, clarke:1579, ...]
      
      [TreeCache] setting cluster properties from xml to: [...]
      


      Recently, an install is logging errors apparently to do with invalid multicast addresses, or improper network interfaces. This seems to be specific to the network config of the PC, but at root we think this is caused by unwanted clustering and/or HA traffic being multicast.

      We intend to deploy a single server, so can anyone recommend a way to turn off all multicasting, clustering and other discovery-based features? We've tried a few things and also seen others posting with similar issues over the past few months but have not found a solution.

        • 1. Re: Clustering and UDP traffic (and errors) in non-clustered

          We don't have a switch to turn clustering on/off. Best way is to build from "default" and then add the service libarary that you need.

          • 2. Re: Clustering and UDP traffic (and errors) in non-clustered

            Thank you for your reply.

            We did start with the "default" configuration, and added our own ejbs, wars etc to the deploy directory. I hope this is what you mean by "build from default" and add a "service library."

            Have I understood your recommendation properly?

            • 3. Re: Clustering and UDP traffic (and errors) in non-clustered

              there is no dependency on clustering in the "default" configuration. If you started with this configuration, it seems likely that you added something which does have a clustering dependency.

              You note that you removed cluster-service.xml. This configuration file isn't included in the default configuration. If you had to remove it, did you start with the "all" configuration instead?

              • 4. Re: Clustering and UDP traffic (and errors) in non-clustered

                Ahh. Thank you Ben and Jerry!

                I now think the issue was the install option I selected when I unpacked the 4.0.3 download. It creates a deploy directory called "default" but I must have clicked the "all" radio button and got that configuration.

                I had missed that change in directory structure, and was accustomed to the old install where we had separate directories for "default," "all" and "minimal" configurations.

                This information may be of use to others who have posted questions with keywords such as: disable clustering, multicast, UDP, standalone deployment.