Can you show us where it exactly blocks (e.g. use Ctrl-Break on windows to print a thread dump)? IndexSearchers methods are not synchronized and concurrent access is easy possible, all concurrent access is managed by the underlying IndexReader. Maybe you synchronize somewhere in your code?
----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -----Original Message----- > From: Paul Taylor [mailto:paul_t...@fastmail.fm] > Sent: Wednesday, August 25, 2010 10:26 PM > To: java-user@lucene.apache.org > Subject: Blocking on IndexSearcher search > > Hi > > My multithreaded code was always creating a new IndexSearcher for every > search, but I changed over to the recommendation of creating just one index > searcher and keeping it between searches. Now I find if I have multiple threads > trying to search they block on the search method(), only one can search at any > time, is this expected behaviour ? > > > Paul > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
