time:[5+TO+300]&wt=javabin&rows=20&version=1}
>
> hits=8 status=0 QTime=297
> 05.11.2009 17:10:25 org.apache.solr.update.SolrIndexWriter finalize
> SEVERE: SolrIndexWriter was not closed prior to finalize(), indicates a
> bug -- POSSIBLE RESOURCE LEAK!!!
>
>
--
View this message
rt=0&q=%2Bstart_date:[*+TO+NOW]+%2Bend_date:[NOW+TO+*]+%2Bruntime:[5+TO+300]&wt=javabin&rows=20&version=1}
>> hits=8 status=0 QTime=297
>> 05.11.2009 17:10:25 org.apache.solr.update.SolrIndexWriter finalize
>> SEVERE: SolrIndexWriter was not closed prior to finalize
nd_date:[NOW+TO+*]+%2Bruntime:[5+TO+300]&wt=javabin&rows=20&version=1}
hits=8 status=0 QTime=297
05.11.2009 17:10:25 org.apache.solr.update.SolrIndexWriter finalize
SEVERE: SolrIndexWriter was not closed prior to finalize(), indicates a
bug -- POSSIBLE RESOURCE LEAK!!!
--
View th
lback
>>>> INFO: end_rollback
>>>> 05.11.2009 16:14:33 org.apache.solr.core.SolrCore execute
>>>> INFO: [sei] webapp=/solr path=/dataimport params={} status=0 QTime=9
>>>> 05.11.2009 16:43:38 org.apache.solr.core.SolrCore execute
>>>> INFO: [epg] webapp=/solr path
: that's what I thought because I didn't experience any problems. But doesn't
: that indicate that there is a missing cleanup?
yes, it does.
: And if it is not worth checking / changing then maybe the log level should be
: decreased to adjust in comparison to other SEVERE warnings?
it really is
It would be really helpful if people seeing these messages frequently in
their logs could elaborate a little bit more on...
1) exactly which version/build of Solr they are using
1.4.0 RC from 30th of October.
Changes.txt contains the line:
$Id: CHANGES.txt 831168 2009-10-30 00:28:25Z yonik $
On Mon, 9 Nov 2009, Chantal Ackermann wrote:
: > common pattern? ... do all of the people noticing these "POSSIBLE RESOURCE
: > LEAK" messages use rollback? is there any correlation between how much
: > you use rollback and how often you get one of these messages? (even if
: > they don't happen
