tracker issue : CF-4198387

select a category, or use search below
(searches all categories and all time range)
Title:

java.lang.OutOfMemoryError: Metaspace

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/Fixed

Reporter/Name(from Bugbase): e-domizil License Team / e-domizil License Team ()

Created: 03/06/2017

Components: Performance

Versions: 2016,2018

Failure Type: Memory Leak

Found In Build/Fixed In Build: Updater 3 / CF2016U12,CF2018U5

Priority/Frequency: Major / All users will encounter

Locale/System: ALL / Win 2012 Server x64

Vote Count: 5

Problem Description: Since we upgraded from CF10 to CF2016 we are running permanently into java.lang.OutOfMemoryError: Metaspace errors. Several tries to increase heap and other stuff has not worked. There seems to be a memory leak.

Mar 03, 2017 5:32:21 PM org.apache.tomcat.util.net.NioEndpoint$SocketProcessor doRun
SEVERE: 
java.lang.OutOfMemoryError: Metaspace

Mar 03, 2017 5:32:53 PM org.apache.tomcat.util.net.NioEndpoint$SocketProcessor doRun
SEVERE: 
java.lang.OutOfMemoryError: Metaspace


Steps to Reproduce: Run CF2016 in production with your apps

Actual Result: System goes out of memory, but has enough free heap space

Expected Result: No out of memory

Any Workarounds: None

Attachments:

Comments:

We are also experiencing massive increase in metaspace vs. CF10.
Vote by Justin T.
29374 | July 23, 2018 07:32:36 PM GMT
Under CF10 we would typically use 300mb of metaspace with a max setting of 750mb. We had to increase to 2GB to stop the out of memory errors. It's using about 800mb of metaspace currently, more than 100% more than CF10.
Comment by Justin T.
29373 | July 23, 2018 07:34:02 PM GMT