-
Task
-
Resolution: Done
-
Major
-
None
-
None
Analysis of the contents of metaspace shows that ParallellBootOperationContext and ParallellBootOperationContext$1 end up in memory multiple times. This indicates a problem with the classloader, for which I'll file a JBoss Modules bug, but a change in WildFly Core can work around the problem.
- is related to
-
MODULES-302 Class first accessed from a concurrently executed Runnable appears multiple times in metaspace
- Resolved
-
JBEAP-6731 Increased Memory footprint in EAP 7.1.0
- Closed