Error java.lang.OutOfMemoryError: getNewTla using Oracle EPM products
- by Marc Schumacher
Running into a Java out of memory error, it is very common behaviour in the field that the Java heap size will be increased. While this
might help to solve a heap space out of memory error, it might not help to fix
an out of memory error for the Thread Local Area (TLA). Increasing the
available heap space from 1 GB to 16 GB might not even help in this situation.
The Thread Local Area (TLA) is part of the Java heap, but as
the name already indicates, this memory area is local to a specific thread so
there is no need to synchronize with other threads using this memory area.
For optimization purposes the TLA size is configurable using the Java command line option “-XXtlasize”. Depending on the JRockit version and the available Java heap, the default values vary.
Using Oracle EPM System (mainly 11.1.2.x) the following setting was tested successfully:
-XXtlasize:min=8k,preferred=128k
More information about the “-XXtlasize” parameter can be
found in the JRockit documentation:
http://docs.oracle.com/cd/E13150_01/jrockit_jvm/jrockit/jrdocs/refman/optionXX.html
