[ 
https://issues.apache.org/jira/browse/SOLR-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13541030#comment-13541030
 ] 

Ahmet Arslan commented on SOLR-2357:
------------------------------------

My restart was an improper shutdown of tomcat. By the way I don't use solr cell.
                
> Thread Local memory leaks on restart
> ------------------------------------
>
>                 Key: SOLR-2357
>                 URL: https://issues.apache.org/jira/browse/SOLR-2357
>             Project: Solr
>          Issue Type: Bug
>          Components: contrib - Solr Cell (Tika extraction), search
>    Affects Versions: 1.4.1
>         Environment: Windows Server 2008, Apache Tomcat 7.0.8, Java 1.6.23
>            Reporter: Gus Heck
>              Labels: memory_leak, threadlocal
>
> Restarting solr (via a changed to a watched resource or via manager app for 
> example) after submitting documents with Solr-Cell, gives the following 
> message (many many times), and causes Tomcat to shutdown completely. 
> SEVERE: The web application [/solr] created a ThreadLocal with key of type 
> [org.
> apache.solr.common.util.DateUtil.ThreadLocalDateFormat] (value 
> [org.apache.solr.
> common.util.DateUtil$ThreadLocalDateFormat@dc30dfa]) and a value of type 
> [java.t
> ext.SimpleDateFormat] (value [java.text.SimpleDateFormat@5af7aed5]) but 
> failed t
> o remove it when the web application was stopped. Threads are going to be 
> renewe
> d over time to try and avoid a probable memory leak.
> Feb 10, 2011 7:17:53 AM org.apache.catalina.loader.WebappClassLoader 
> checkThread
> LocalMapForLeaks

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to