Classes get saved in PermGen and are never freed. Apparently there are
JVM options to fix this.
I'm not sure if the old String.intern() use in Lucene had this problem.
Lance
On Wed, Mar 2, 2011 at 10:23 PM, Chris Hostetter
wrote:
>
> : When I did heap analysis, the culprit always seems to
> : be
: When I did heap analysis, the culprit always seems to
: be TimeLimitedCollector thread. Because of this, considerable amount of
: classes are not getting unloaded.
...
: > > There are couple of JIRA's related to this:
: > > https://issues.apache.org/jira/browse/LUCENE-2237,
: > > https:/
Thanks for the suggestions. Tomcat does release permgen memory with
appropriate jvm options and configuration settings (
clearReferencesStopTimerThreads, clearReferencesThreadLocals).
When I did heap analysis, the culprit always seems to
be TimeLimitedCollector thread. Because of this, considerable
Hi,
I remember reading somewhere that undeploying an application in Tomcat won't
release memory, thus repeating the cycle will indeed exhaust the permgen. You
could enable garbage collection of the permgen.
HotSpot can do this for you but it depends on using CMS which you might not
want to us
Hi
I get the same problem on tomcat with other applications, so this does not
appear to be limited to SOLR. I got the error on tomcat 6 and 7. The only
solution I found was to kill tomcat and start it again.
François
On Mar 2, 2011, at 2:28 PM, Search Learn wrote:
> Hello,
> We currently depl
Hi
I get the same problem on tomcat with other applications, so this does not
appear to be limited to SOLR. I got the error on tomcat 6 and 7. The only
solution I found was to kill tomcat and start it again.
François
On Mar 2, 2011, at 2:28 PM, Search Learn wrote:
> Hello,
> We currently depl
