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
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  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 | 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]
  3. 0

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

    grokbase.com | 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]
  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]

    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