Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-1292

SocketBindingManager.createMulticast/DatagramSocket(...) variants needed for unbound sockets

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 2.0.8.Final
    • 2.0.5.Final
    • Server
    • None

      In order to modify the SO_REUSEADDR option of a multicast or datagram socket, the socket must be unbound - otherwise the behavior is undefined. See:
      http://docs.oracle.com/javase/8/docs/api/java/net/DatagramSocket.html#setReuseAddress-boolean-

      To support this (as required for JGroups 3.6.7.Final), SocketBindingManager needs methods to create unbound datagram/multicast sockets. The current methods that accept a SocketAddress throw an ISE when a null address is used.

      Setting priority to blocker to encourage inclusion into 2.0.x.

              pferraro@redhat.com Paul Ferraro
              pferraro@redhat.com Paul Ferraro
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: