java.net.BindException: Cannot assign requested address: set socket option failed

Oracle Community | 3004 | 1 decade ago
  1. 0

    Multicast, WLS 7.0 and Win 2000

    Oracle Community | 1 decade ago | 3004
    java.net.BindException: Cannot assign requested address: set socket option failed
  2. 0

    Problems starting reggie on win2000

    Google Groups | 2 decades ago | Steve robinson
    java.net.BindException: Cannot assign requested address: set socket option failed
  3. 0
    This seems to be caused by too many connections to the same server, saturating it and causing the exception! More info on the link
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.net.BindException

      Cannot assign requested address: set socket option failed

      at java.net.PlainDatagramSocketImpl.join()
    2. Java RT
      MulticastSocket.joinGroup
      1. java.net.PlainDatagramSocketImpl.join(Native Method)
      2. java.net.MulticastSocket.joinGroup(MulticastSocket.java:229)
      2 frames
    3. weblogic.cluster
      ClusterCommunicationService.initialize
      1. weblogic.cluster.FragmentSocket.start(FragmentSocket.java:111)
      2. weblogic.cluster.MulticastManager.startListening(MulticastManager.java:140)
      3. weblogic.cluster.ClusterCommunicationService.initialize(ClusterCommunicationService.java:51)
      3 frames
    4. weblogic.t3.srvr
      T3Srvr.run
      1. weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:779)
      2. weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
      3. weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
      3 frames
    5. weblogic
      Server.main
      1. weblogic.Server.main(Server.java:31)
      1 frame