- Status:Verified(View Workflow)
- Resolution: Done
- Fix Version/s:6.4.0
- Labels:
- Environment:
Java.lang.outofmemoryerror Metaspace Jboss
Standalone configuration files (standalone.conf, standalone.conf.bat and standalone.conf.ps1 on EAP7) define very low upper bound for Metaspace size (256m). With this out-of-the-box settings, user is going to hit OOME after accessing Business Central and standalone BAM (Dashbuilder). To provide smooth user experience, let's increase the maximum Metaspace size during productization process. I propose 1G.
Remove the -XX:MaxMetaspaceSize parameter entirely, since Java 8 automatically increases the MetaSpace area as needed. Alternatively, increase the XX:MaxMetaspaceSize value. Sources: About G1 Garbage Collector, Permanent Generation and Metaspace; Java Platform, Standard Edition HotSpot Virtual Machine Garbage Collection Tuning Guide.
- Caused by: java.lang.OutOfMemoryError: Metaspace Environment. DXP 7.0; Resolution. Go to$Tomcat-home/bin and on the file.
- Recently it started failing during the deploy of a large application with 'java.lang.OutOfMemoryError: Metaspace' errors. Experimenting with the command-line metaspace configuration flags made no difference. The only thing that did work was to disable CMS.
- Assignee:
- Cheng Zhang
- Reporter:
- Jiří Locker
- Tester:
- Jiří Locker
- Votes:
- 0Vote for this issue
- Watchers:
- 3Start watching this issue
Java.lang.outofmemoryerror Metaspace Wildfly
- Created:
- Updated:
- Resolved: