getting java thread id smoke-stack snippet run-away java thread
on busiest prolongation installation, arise i unparalleled thread seems stranded an enormous loop. i've managed figure out culprit, after many investigate debugging, nonetheless seems should possible. here bloody details:
current debugging notes:
1) ps -el 18975 shows me the linux pid problem child thread, 19269
$ps -el | grep 18975
...
pid lwp tty cmd
18975 18994 ? 00:00:05 java
18975 19268 ? 00:00:00 java
18975 19269 ? 05:16:49 java
18975 19271 ? 00:01:22 java
18975 19273 ? 00:00:00 java
...
2) jstack -l 18975 says there deadlocks, jstack -m 18975 does work
3) jstack -l 18975 does give me smoke-stack snippet threads (~400). instance thread smoke-stack (and problem):
"http-342.877.573.944-8080-360" daemon prio=10 tid=0x0000002adaba9c00 nid=0x754c object.wait() [0x00000000595bc000..0x00000000595bccb0]
java.lang.thread.state: sharp (on vigilant monitor)
during java.lang.object.wait(native method)
- sharp (a org.apache.tomcat.util.net.jioendpoint$worker)
during java.lang.object.wait(object.java:485)
during org.apache.tomcat.util.net.jioendpoint$worker.await(jioendpoint.java:416)
- sealed (a org.apache.tomcat.util.net.jioendpoint$worker)
during org.apache.tomcat.util.net.jioendpoint$worker.run(jioendpoint.java:442)
during java.lang.thread.run(thread.java:619)
4) ps -el output's thread id does review cost jstack, during slightest i can't it. (jstack support bit sparse.)
5) there complicated io, memory use analogous activity clues work with.
platform:
- java 6
- tomcat 6
- rhel 4 (64-bit)
does anybody know i tie linux ps cost problem child java thread? close, nonetheless far...
Comments
Post a Comment