Posted: 5 Oct 2017 5:33 EDT Last activity: 16 Oct 2018 12:03 EDT
java.lang.OutOfMemoryError:Metaspace error in logs for Pega7.3 using Java 8
We have Pega 7.3 using Java 8+tomcat and one of the JVM arguments (due to Java 8) is MaxMetaspaceSize instead of PermGen. The value of the arg is XX:MaxMetaspaceSize=1024m . The other day JVM crashed with error in logs java.lang.OutOfMemoryError:Metaspace. It produced a crash dump file when trying to stop the tomcat & it required cleaning application server cache to get the application up & running.
I see below args as a recommendation on one of the stackoverflow articles
Has any one had this issue? Are there any alternate fixes available? We had errors in logs related to listeners(OOTB CPM listeners failing email account authentication) but they should not be contributing to the JVM crash?
No db related log errors. It is a multi-tenant env. Any inputs will be highly appreciated!
Thanks in advance!
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
The above Error indicates that the reserved native memory for Classes Metadata is exhausted for your application. Instead of applying the JVM argument recommended in stackoverflow.com, I would think increasing the -XX:MetaspaceSize=2048M and monitoring its growth is a better option. Even after increasing if you still encounter the same Error after a period of time, that would indicate a leak and may actually be related to the issue reported under link - https://issues.apache.org/jira/browse/CXF-2939
Thanks Ankur for quick response ! Will try increasing the Metaspacesize to 2048.
I wonder if this also points to any specific issue in application? I assume the number of classes being loaded(and thereby metadata) varies from application to application? Is there anything you would want me to check around possible memory leak ? (this is client hosted & not on pega cloud)
Note: the issue reported in the link you provided, has been mentioned in the stackoverflow article I mentioned above & they both point to same solution :)
Thank you for posting your query on PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write a Post button that’s available on the top right pane of this page. Once created, please reply back here with the URL of the new post.
We have also sent you a private message opening up a communication channel in case you have any further questions.