Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-4181

If -b 0.0.0.0 is used, do not pass wildcard addresss through to JGroups

    XMLWordPrintable

Details

    Description

      If JGroups tries to bind to 0.0.0.0 you get nasty effects like:

      11:00:42,765 ERROR [UDP] failed sending message to 0.0.0.0:2902 (0 bytes)
      java.net.BindException: Cannot assign requested address: Datagram send failed
      at java.net.PlainDatagramSocketImpl.send(Native Method)
      at java.net.DatagramSocket.send(DatagramSocket.java:612)
      at org.jgroups.protocols.UDP._send(UDP.java:338)
      at org.jgroups.protocols.UDP.sendToSingleMember(UDP.java:299)
      at org.jgroups.protocols.TP.doSend(TP.java:940)
      at org.jgroups.protocols.TP.send(TP.java:926)
      at org.jgroups.protocols.TP.down(TP.java:712)
      at org.jgroups.stack.Protocol.receiveDownEvent(Protocol.java:517)
      at org.jgroups.stack.Protocol.passDown(Protocol.java:551)
      at org.jgroups.protocols.Discovery.up(Discovery.java:246)
      at org.jgroups.stack.Protocol.receiveUpEvent(Protocol.java:488)
      at org.jgroups.stack.Protocol.passUp(Protocol.java:538)
      at org.jgroups.protocols.TP.handleIncomingMessage(TP.java:908)
      at org.jgroups.protocols.TP.handleIncomingPacket(TP.java:850)
      at org.jgroups.protocols.TP.access$400(TP.java:45)
      at org.jgroups.protocols.TP$IncomingPacketHandler.run(TP.java:1296)
      at java.lang.Thread.run(Thread.java:595)
      11:00:42,796 WARN [NAKACK] 0.0.0.0:4627] discarded message from non-member 0.0.
      0.0:2898, my view is [0.0.0.0:4627|0] [0.0.0.0:4627]

      Fix is in org.jboss.Main to pass the -b value through ServerConfigUtil.fixRemoteAddress(), which will return pick a non-wildcard address via InetAddress.getLocalHost().getHostName().

      Attachments

        Activity

          People

            bstansbe@redhat.com Brian Stansberry
            bstansbe@redhat.com Brian Stansberry
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: