java.net.SocketException: Connection reset the out of memory error is repeated 41 times. After all the cpu load gone down to zero and the server stoped responding (no wonder without free threads or memory). The thread dump (can be submitted if someone is interested) contains 678 threads waiting on 9 JspServletWrapper Objects ( The nine looks like: "http-8580-Processor16777" daemon prio=1 tid=0xc40b5890 nid=0x236f waiting for monitor entry [0xc13fe000..0xc13ff840]

tomcat-users | Leon Rosenberg | 1 decade ago
  1. 0

    Deadlock -> Out of Threads -> Strange Exception -> OutOfMemory -> Server Death. Bug in org.apache.naming.resources.ProxyDirContext.cacheLoad?

    apache.org | 1 year ago
    java.net.SocketException: Connection reset the out of memory error is repeated 41 times. After all the cpu load gone down to zero and the server stoped responding (no wonder without free threads or memory). The thread dump (can be submitted if someone is interested) contains 678 threads waiting on 9 JspServletWrapper Objects ( The nine looks like: "http-8580-Processor16777" daemon prio=1 tid=0xc40b5890 nid=0x236f waiting for monitor entry [0xc13fe000..0xc13ff840]
  2. 0

    Re: Deadlock -> Out of Threads -> Strange Exception -> OutOfMemory -> Server Death. Bug in org.apache.naming.resources.ProxyDirContext.cacheLoad?

    apache.org | 11 months ago
    java.net.SocketException: Connection reset the out of memory error is repeated 41 times. After all the cpu load gone down to zero and the server stoped responding (no wonder without free threads or memory). The thread dump (can be submitted if someone is interested) contains 678 threads waiting on 9 JspServletWrapper Objects ( The nine looks like: "http-8580-Processor16777" daemon prio=1 tid=0xc40b5890 nid=0x236f waiting for monitor entry [0xc13fe000..0xc13ff840]
  3. 0

    [Tomcat-users] Deadlock -> Out of Threads -> Strange Exception -> OutOfMemory -> Server Death. Bug in org.apache.naming.resources.ProxyDirContext.cacheLoad? - Grokbase

    grokbase.com | 11 months ago
    java.net.SocketException: Connection reset the out of memory error is repeated 41 times. After all the cpu load gone down to zero and the server stoped responding (no wonder without free threads or memory). The thread dump (can be submitted if someone is interested) contains 678 threads waiting on 9 JspServletWrapper Objects ( The nine looks like: "http-8580-Processor16777" daemon prio=1 tid=0xc40b5890 nid=0x236f waiting for monitor entry [0xc13fe000..0xc13ff840]
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Deadlock -> Out of Threads -> Strange Exception -> OutOfMemory -> Server Death. Bug in org.apache.naming.resources.ProxyDirContext.cacheLoad?

    tomcat-users | 1 decade ago | Leon Rosenberg
    java.net.SocketException: Connection reset the out of memory error is repeated 41 times. After all the cpu load gone down to zero and the server stoped responding (no wonder without free threads or memory). The thread dump (can be submitted if someone is interested) contains 678 threads waiting on 9 JspServletWrapper Objects ( The nine looks like: "http-8580-Processor16777" daemon prio=1 tid=0xc40b5890 nid=0x236f waiting for monitor entry [0xc13fe000..0xc13ff840]
  6. 0

    Sudden increase in open file descriptors

    Oracle Community | 1 decade ago | 666705
    java.net.SocketException: Too many open files" When our internet application stopped responding I immediately checked the number of open file descriptors on my Solaris machine by using the "lsof" command and found that it was an abnormal 600 value and as I continued monitoring it reached 1024 in matter of minutes and WebLogic gave the above exception. The current setting for file descriptors is 1024. But all these days the average number of open file descriptors was well below 220. I also took thread dumps and found that most of the threads were stuck at the following location ""ExecuteThread: '3' for queue: 'weblogic.kernel.Default'" daemon prio=5 tid=0x00883a90 nid=0x10 runnable [6d080000..6d0819c0]

    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

      Connection reset the out of memory error is repeated 41 times. After all the cpu load gone down to zero and the server stoped responding (no wonder without free threads or memory). The thread dump (can be submitted if someone is interested) contains 678 threads waiting on 9 JspServletWrapper Objects ( The nine looks like: "http-8580-Processor16777" daemon prio=1 tid=0xc40b5890 nid=0x236f waiting for monitor entry [0xc13fe000..0xc13ff840]

      at org.apache.naming.resources.ProxyDirContext.cacheLoad()
    2. Web Container Naming Utilities
      ProxyDirContext.cacheLoad
      1. org.apache.naming.resources.ProxyDirContext.cacheLoad(ProxyDirContext.java:1552)
      1 frame