lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andre Bois-Crettez <andre.b...@kelkoo.com>
Subject Re: solr 3.4: memory leak?
Date Thu, 11 Apr 2013 12:01:38 GMT
On 04/11/2013 08:49 AM, Dmitry Kan wrote:
> SEVERE: The web application [/solr] appears to have started a thread named
> [MultiThreadedHttpConnectionManager cleanup] but has failed to stop it.
> This is very likely to create a memory leak.
> Apr 11, 2013 6:38:14 AM org.apache.catalina.loader.WebappClassLoader
> clearThreadLocalMap

To my understanding this kind of leak only is a problem if the Java code
is *reloaded* while the tomcat JVM is not stopped.
For example when reloadable="true" in the Context of the web application
and you change files in WEB-INF or .war : what would happen is that each
existing threadlocals would continue to live (potentially holding
references to other stuff and preventing GC) while new threadlocals are
created.

http://wiki.apache.org/tomcat/MemoryLeakProtection

If you stop tomcat entirely each time, you should be safe.


--
André Bois-Crettez

Search technology, Kelkoo
http://www.kelkoo.com/


Kelkoo SAS
Société par Actions Simplifiée
Au capital de € 4.168.964,30
Siège social : 8, rue du Sentier 75002 Paris
425 093 069 RCS Paris

Ce message et les pièces jointes sont confidentiels et établis à l'attention exclusive
de leurs destinataires. Si vous n'êtes pas le destinataire de ce message, merci de le détruire
et d'en avertir l'expéditeur.

Mime
View raw message