> > > I have a app that seems to be locking on some search calls. I am > including > > the stacktrace for the blocked and blocker thread. >
Is it daedlock for sure? No search deadlock fixes were done since 2.1.0, so perhaps it is something else... > "TP-Processor177" daemon prio=10 tid=0x0000002c8a96c800 nid=0x769d > > waiting for monitor entry [0x000000004e60a000..0x000000004e60dcb0] > > java.lang.Thread.State: BLOCKED (on object monitor) > > at > org.apache.lucene.index.SegmentReader.norms(SegmentReader.java:450) > > - locked <0x0000002aa0a4f5a8> (a > org.apache.lucene.index.SegmentReader) > Indeed this guy is blocked. > Here is the executing thread that is doing the blocking But this guy seems to be running...? > "TP-Processor97" daemon prio=10 tid=0x0000002c8fe35400 nid=0x75ce > runnable [0x00000000497bc000..0x00000000497bfdb0] > java.lang.Thread.State: RUNNABLE > at org.apache.lucene.index.SegmentReader.isDeleted(SegmentReader.java:346) > at org.apache.lucene.index.IndexReader.document(IndexReader.java:368) > at org.apache.lucene.search.IndexSearcher.doc(IndexSearcher.java:84) > at org.apache.lucene.search.Hits.doc(Hits.java:104) Also, not sure for how many docs your app is loading like this (calling Hits.docs()), but documents loading is costly... is there a chance that many docs are being loaded and things just take long, not a deadlock? Doron
