3 Replies Latest reply on Aug 12, 2004 10:53 AM by belaban

    bind_addr ignored?

    peterb
    peterb Aug 11, 2004 9:24 AM

      I have a clustered machine with 2 interfaces that's using TCP and TCPPING to connect and have specified the bind_addr both in the TCP protocol and through the --host switch. However the DefaultPartition keeps reporting the other interface address as the node name.

      This results in faulty HAJNDI lookups because it reports a different address than the one on which JBoss is listening.

      Any one have any ideas? Have I missed some configuration parameter?

      • 4611 Views
      • Tags:
        • 1. Re: bind_addr ignored?
          peterb
          peterb Aug 11, 2004 11:34 AM (in response to peterb)

          I figured it out myself. Apparently what I wanted is not possible in 3.2.2 but it is in 3.2.5. In 3.2.5 (and possibly earlier version too, but certainly not 3.2.2) The ClusterPartition mbean has a NodeAddress attribute which can be set to the correct bind address.

            • Actions
          • 2. Re: bind_addr ignored?
            belaban
            belaban Aug 12, 2004 10:52 AM (in response to peterb)

            I fixed this in the CVS. Did it for UDP, but apparently forgot TCP...
            Bela

              • Actions
            • 3. Re: bind_addr ignored?
              belaban
              belaban Aug 12, 2004 10:53 AM (in response to peterb)

              BTW: the --host switch suffices here, no need for bind_addr in the parameters for JGroups.

              Bela

                • Actions