Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via grokbase.com by Unknown author, 2 years ago
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
via apache.org by Unknown author, 2 years ago
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
via tomcat-users by Leon Rosenberg, 1 year ago
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
via apache.org by Unknown author, 2 years ago
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
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(ProxyDirContext.java:1552)