java.net.SocketException: fd=1848: socket was closed on this end

Oracle Community | 3004 | 2 decades ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    What is this? Are the keys corrupt?

    Oracle Community | 2 decades ago | 3004
    java.net.SocketException: fd=1848: socket was closed on this end
  2. 0

    java.net.SocketException: fd=1992: socket was closed on this end

    Google Groups | 2 decades ago | Rashmi
    java.net.SocketException: fd=1992: socket was closed on this end
  3. 0

    exception in server

    Google Groups | 2 decades ago | Sanjay Ungarala
    java.net.SocketException: fd=1168: socket was closed on this end
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    SocketException

    Google Groups | 2 decades ago | Sanjay Ungarala
    java.net.SocketException: fd=1168: socket was closed on this end
  6. 0

    SocketException

    Oracle Community | 2 decades ago | 3004
    java.net.SocketException: fd=1168: socket was closed on this end

    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.SocketException

      fd=1848: socket was closed on this end

      at weblogic.socket.NTSocketMuxer.initiateIO()
    2. weblogic.socket
      SocketReaderRequest.execute
      1. weblogic.socket.NTSocketMuxer.initiateIO(Native Method)
      2. weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:632)
      3. weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:23)
      3 frames
    3. weblogic.kernel
      ExecuteThread.run
      1. weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
      2. weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
      2 frames