liang xie created HBASE-7449: -------------------------------- Summary: Refine UseMembar detail Key: HBASE-7449 URL: https://issues.apache.org/jira/browse/HBASE-7449 Project: HBase Issue Type: Improvement Components: documentation Affects Versions: 0.96.0 Environment: $ uname -a Linux lg-hadoop-control01.bj 2.6.32-279.el6.x86_64 #1 SMP Fri Jun 22 12:19:21 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
$ java -version java version "1.6.0_37" Java(TM) SE Runtime Environment (build 1.6.0_37-b06) Java HotSpot(TM) 64-Bit Server VM (build 20.12-b01, mixed mode) Reporter: liang xie Assignee: liang xie Priority: Trivial we encountered a hung issue, the thread dump shows: most of threads waiting to a lock but there isn't lock holder be found We know there were some discuss before, e.g: https://issues.apache.org/jira/browse/HBASE-3622 http://bugs.sun.com/view_bug.do?bug_id=6822370 http://cs.oswego.edu/pipermail/concurrency-interest/2012-August/009635.html https://blogs.oracle.com/dave/entry/a_race_in_locksupport_park My point is that the JVM bug is still not fixed(at least for latest 1.6.0_37, the hotspot version: 20.12-b01), it's not just a old JVM issue, let's update the trouble shooting document firstly if possible. I'm trying to reproduce with a debug openjdk version in-house. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira