[
https://issues.apache.org/jira/browse/SOLR-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14080859#comment-14080859
]
Shawn Heisey commented on SOLR-6303:
------------------------------------
While I agree that this is a bug that needs fixing, I believe there are also
other memory leak problems when restarting the application instead of the
entire servlet container. Because I was told about the other problem by some
extremely smart people that love to fix bugs, I suspect that it is not at all
easy to fix. If I'm wrong, everyone please feel free to ignore me.
There are two recommended ways to get Solr to notice a new configuration,
depending on exactly what got changed: Reload the core/collection, or restart
the entire servlet container. Reloading the core handles almost all config
changes, restarting the container gets everything else.
> JDBC drivers not being released causing permgen memory leak
> ------------------------------------------------------------
>
> Key: SOLR-6303
> URL: https://issues.apache.org/jira/browse/SOLR-6303
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.9
> Environment: Debian 7
> OpenJDK Runtime Environment (IcedTea 2.5.1) (7u65-2.5.1-2~deb7u1)
> Apache Tomcat 7.0.28
> Solr 4.9.0
> Reporter: Robin Grindrod
>
> I have an issue where after reloading Solr a few times Tomcat runs out of
> permgen space. After a little bit of investigation it seems that if I reload
> Solr without running the DataImportHandler and then perform garbage
> collection the amount of used permgen memory seems to return to roughly where
> it was before. However, if I run the DataImportHandler and then reload, the
> amount of memory will not return to where it was before. If this is repeated
> a few times it will eventually cause Tomcat to hang and throw a
> "java.lang.OutOfMemoryError: PermGen space" error.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
