12 Replies Latest reply on Oct 19, 2004 5:22 AM by belaban

    UDP bind_addr vs.  -Dbind.address JBoss 3.2.6

    sheckler

      Hi all,

      testing JBoss 3.2.6 I found neither UDP bind_addr=1.2.3.4 nor
      -Dbind.address=1.2.3.4 seem to have any effect on JGroups binding.

      The bindaddress used is in both cases is the one set by -b as argument for org.jboss.Main.

      How can I set a special bind address for JGroups with JBoss 3.2.6?

      Thanks
      Stefan

        • 1. Re: [ERROR] NAKACK.handleXmitReq()
          belaban

          Hi Sacha,

          I am still getting the same error after incorporating the changes as suggested by you in cluster-service.xml. It has been observed that the error:”
          2004-03-28 02:47:27,450 DEBUG [org.javagroups.DefaultPartition] [Sun Mar 28 02:47:27 EST 2004] [ERROR] NAKACK.handleXmitRe
          q(): (requester=choqtap4:32794 (additional data: 19 bytes)) message with seqno=0 not found in sent_msgs ! sent_msgs=18 17
          16 15 14 13 12 11 10 9 8 7 6 5” comes when other node in cluster says suspected member and then jboss starts throwing that "message seqno=" error. It comes in high load and creates 20 MB server.log file in each 3 min.


          Regards,
          Monu

          • 2. Re: UDP bind_addr vs.  -Dbind.address JBoss 3.2.6
            dfisher

            Were you able to get JGroups to bind to a specific IP address?
            I've tried using -b, --host, -Djboss.bind.address, and setting the address in the cluster-service.xml file.
            None of these have worked.
            JGroups always binds to all interfaces.

            • 3. Re: UDP bind_addr vs.  -Dbind.address JBoss 3.2.6
              starksm64

              Yes, I see the same issue. I have create a bug report on sourceforge:

              http://sourceforge.net/tracker/index.php?func=detail&aid=1050899&group_id=22866&atid=376685

              • 4. Re: UDP bind_addr vs.  -Dbind.address JBoss 3.2.6
                starksm64

                This is an artifact of the jdk1.3 MulticastSocket interface. Only jdk 1.4 has an ability to set the bind address of the socket. The jboss bind address is passed to the MulticastSocket via the setInterface(InetAddress) method so mcast traffic is sent to the desired interface even though the socket does not appear to be bound to it.

                • 5. Re: UDP bind_addr vs.  -Dbind.address JBoss 3.2.6
                  sheckler

                  I used the UDP bind_addr attribute in cluster-service.xml to bind JGroups to a different lan interface as set by -b bindaddress on JBoss startup (multihomed machine, two parallel networks).
                  This does not work with 3.2.6 (and did with 3.2.5).

                  Stefan Heckler
                  PSI AG, Germany

                  • 6. Re: UDP bind_addr vs.  -Dbind.address JBoss 3.2.6
                    adrian.brock

                    "It does not work" isn't going to get you very many answers.
                    My answer with the same level of thought should be "It works for me."

                    You do know there's a separate channel in 3.2.6 for http session clustering in
                    deploy/tc5-cluster-service.xml?

                    • 7. Re: UDP bind_addr vs.  -Dbind.address JBoss 3.2.6
                      belaban

                      I just re-ran 3.2.6:

                      run.sh -b 127.0.0.1 -c all

                      and it *did* bind to the correct address.

                      In 3.2.6, if you use -b or --host, then this *overrides* the UDP.bind_addr property in the cluster-service.xml

                      Bela

                      • 8. Re: UDP bind_addr vs.  -Dbind.address JBoss 3.2.6
                        sheckler

                        Yes, that is exactely my problem. I want the clustering bind to an other lan address than the jboss instance does to and this is working with 3.2.5. The -b option should n o t override the UDP.bind_addr for my purpose.

                        May be the physical network configuration I have to consider shoud better be changed. If the new behaviour of JBoss 3.2.6 is the correct, planned behaviour I will have talk to my network people. Will this behaviour stay like this in future?

                        Thanks fir Your answer in advance
                        Stefan


                        • 9. Re: UDP bind_addr vs.  -Dbind.address JBoss 3.2.6
                          belaban

                           

                          "sheckler" wrote:
                          Yes, that is exactely my problem. I want the clustering bind to an other lan address than the jboss instance does to and this is working with 3.2.5. The -b option should n o t override the UDP.bind_addr for my purpose.

                          May be the physical network configuration I have to consider shoud better be changed. If the new behaviour of JBoss 3.2.6 is the correct, planned behaviour I will have talk to my network people. Will this behaviour stay like this in future?

                          Thanks fir Your answer in advance
                          Stefan




                          Yes, as I said: n 3.2.6, if you use -b or --host, then this *overrides* the UDP.bind_addr property in the cluster-service.xml .


                          Let me know if this is a problem for you. An option might be to add another system prop that ignore the -Dbind.address property.

                          Bela

                          • 10. Re: UDP bind_addr vs.  -Dbind.address JBoss 3.2.6
                            sheckler

                            It was definitely a problem because we had one physical application server with two lan interfaces (multihomed). The two lans where logically seperate. On this host we ran 2 jboss instances as cluster. Each instance binding to one of the lan interfaces, but the clustering bound to one of the 2 interfaces for both instances (because otherwise they could not see each other using UDP).

                            We solved this problem meanwhile by changing the lan configuration. The two lans are no longer logically seperate. The machines have now two lan addresses within the same subnet.

                            We have this all because we are building a HA mission control system with jboss in addition to a existing HA power supply control system and we are sharing the network configuration which is designed for high redundancy.

                            So it will work by now

                            Thanks for Your help

                            Stefan

                            • 11. Re: UDP bind_addr vs.  -Dbind.address JBoss 3.2.6
                              belaban

                              So do you want me to add that 'ignore.bind.address' system prop now, or not ?

                              Bela

                              • 12. Re: UDP bind_addr vs.  -Dbind.address JBoss 3.2.6
                                mkprim

                                I would be pleased if you could add this to new versions, because I really need that the cluster traffic go through my internal network and not to the external addres (that has a public address).
                                Thanks,
                                Marcelo.