and CachingWrapperFilter are used. I tried looking into Lucene
code also a bit, but couldn't find any clues.
Does anyone have any pointers as to why this could be happening ?
Thanks!
Abhay
--
View this message in context:
http://lucene.472066.n3.nabble.com/Memory-leak-with-Lucene-Search-tp3162070p3162070
anyone have any pointers as to why this could be happening ?
Thanks!
Abhay
--
View this message in context:
http://lucene.472066.n3.nabble.com/Memory-leak-with-Lucene-Search-tp3162070p3162070.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com
understanding is wrong, there is a memory leak for Lucene
search
from Lucene-1195.(svn r659602, May23,2008)
This patch brings in a ThreadLocal cache to TermInfosReader.
It's usually recommended to keep the reader open, and reuse it when
possible. In a common J2EE application, the http requests
appropriate there. It does seem like a problem though and I'm not sure of
the alternative just yet.
On Sep 7, 2008, at 1:35 AM, Chris Lu wrote:
Unless my understanding is wrong, there is a memory leak for Lucene search
from Lucene-1195.(svn r659602, May23,2008)
This patch brings
Unless my understanding is wrong, there is a memory leak for Lucene search
from Lucene-1195.(svn r659602, May23,2008)
This patch brings in a ThreadLocal cache to TermInfosReader.
It's usually recommended to keep the reader open, and reuse it when
possible. In a common J2EE application, the http