Hi.

Today I saw a new (for me) error and i'm not sure why it happened :(

We are using Lucen.Net 2.9.2.2 and the search index is on remote shared
folder.
I think the remote shared folder is the reason for the problem in
combination with many writes to the search index, but not sure.


I can agree about that the searcher will crash with some exception, but the
exception is not catch-able and will terminate the IIS application instead
of only throwing the exception.

I have found a simular bug,LUCENENET-442, do you think that fix also will
fix the case below?


Exception in event log
-----------------------------------------
An unhandled exception occurred and the process was terminated.

Application ID: /LM/W3SVC/10/ROOT

Process ID: 1580

Exception: System.NullReferenceException

Message: Object reference not set to an instance of an object.

StackTrace:    at Lucene.Net.Search.BooleanQuery.Rewrite(IndexReader reader)
   at Lucene.Net.Search.BooleanQuery.Rewrite(IndexReader reader)
   at Lucene.Net.Search.IndexSearcher.Rewrite(Query original)
   at Lucene.Net.Search.Query.Weight(Searcher searcher)
   at Lucene.Net.Search.QueryWrapperFilter.GetDocIdSet(IndexReader reader)
   at Lucene.Net.Search.CachingWrapperFilter.GetDocIdSet(IndexReader reader)
   at Lucene.Net.Search.IndexSearcher.SearchWithFilter(IndexReader reader,
Weight weight, Filter filter, Collector collector)
   at Lucene.Net.Search.IndexSearcher.Search(Weight weight, Filter filter,
Collector collector)
   at Lucene.Net.Search.IndexSearcher.Search(Weight weight, Filter filter,
Int32 nDocs)
   at Lucene.Net.Search.MultiSearcherThread.Run()
   at System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

// Patric

Reply via email to