You are viewing a plain text version of this content. The canonical link for it is here.

Posted to solr-user@lucene.apache.org by Stu Hood <st...@webmail.us> on 2007/10/17 22:46:56 UTC

Solr + Tomcat Undeploy Leaks

Hello,

I'm using the Tomcat Manager app with 6.0.14 to start and stop Solr instances, and I believe I am running into a variant of the linked issue:

http://wiki.apache.org/jakarta-commons/Logging/UndeployMemoryLeak?action=print

According to `top`, the 'size' of the Tomcat process reaches the limit I have set for it with the Java -Xmx flag soon after starting and launching a few instances. The 'RSS' varies based on how full the caches are at any particular time, but I don't think it ever reaches the 'size'.

After a few days, I will get OOM errors in the logs when I try and start new instances (note: this is typically in the middle of the night, when usage is low), and all of the instances will stop responding until I (hard) restart Tomcat.

------------------------

Has anyone run into this issue before? Is logging the culprit? If so, what options do I have (besides setting up a cron job to restart Tomcat nightly...)

Thanks,

Stu Hood
Webmail.us
"You manage your business. We'll manage your email."®