lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "George Aroush" <>
Subject RE: Possible bug(s) in SegmentReader and TermInfosReader
Date Thu, 29 Mar 2007 11:14:47 GMT
Hi Vova,

I have posted your question to the Lucene.Net mailing list.  Please
subscribe so you can post directly and actually read any response to your
question.  See the section "Mailing Lists" for how to subscribe.  Basically,
just send an email to and /

-- George Aroush

-----Original Message-----
From: Vova Tymchenko [] 
Sent: Thursday, March 29, 2007 5:38 AM
Subject: Possible bug(s) in SegmentReader and TermInfosReader

Hello everybody,

I'm using Lucene.Net with my own implementation of Directory which stores
the files in the SQL database.
Additionally, it maintains the reference count for the locks created in the
directory. One thing I noticed is that there are locks left behind
sometimes. Eventually, I tracked the problem down to SegmentReader.

The trouble that I see with SegmentReader (and TermInfosReader as well) is
that it stores references to TermVectorsReader in ThreadLocalStore when
GetTermVectorsReader is called, but .Close method fails to close and clean
up that reference.

The change that I've implemented in my local copy of Lucene (and which seems
to work) is like this - I added the following code to the beginning of
DoClose in SegmentReader:

            TermVectorsReader tvReader = (TermVectorsReader)

            if (tvReader != null)
                System.Threading.Thread.SetData(termVectorsLocal, null);

The following change has been done to TermInfosReader:

            SegmentTermEnum termEnum = (SegmentTermEnum)

            if (termEnum != null)
                System.Threading.Thread.SetData(enumerators, null);


Get your own web address.  
Have a HUGE year through Yahoo! Small Business.

View raw message