[
https://issues.apache.org/jira/browse/SOLR-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13704537#comment-13704537
]
Dawid Weiss commented on SOLR-5022:
-----------------------------------
The easiest way to check would be to expose/inspect permgen stats. For just the
number of classes you can run the VM with:
java ... -XX:+TraceClassLoading | grep "[Loading" | wc -l
which will give you the number of classes loaded by the VM once it exits. The
memory pools can also be checked from within the VM (as in the example above)
-- we could actually add an assertion to LuceneTestCase that would monitor the
use of permgen and throw an assertion if, say, 90% of the maximum permgen space
is used. This would prevent permgen-related process-hung-forever issues, at
least it'd be an attempt to detect them early.
> PermGen exhausted test failures on Jenkins.
> -------------------------------------------
>
> Key: SOLR-5022
> URL: https://issues.apache.org/jira/browse/SOLR-5022
> Project: Solr
> Issue Type: Test
> Components: Tests
> Reporter: Mark Miller
> Fix For: 5.0, 4.4
>
> Attachments: intern-count-win.txt, SOLR-5022.patch
>
>
--
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: [email protected]
For additional commands, e-mail: [email protected]
