Error java.lang.OutOfMemoryError: getNewTla using Oracle EPM products

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:


More information about the “-XXtlasize” parameter can be found in the JRockit documentation:


With above paramters you still see crash with getnewTLA OOM error then set the following:


Posted by Ahmed on July 10, 2013 at 04:57 PM PDT #

[ERROR] Argument error: -XXtlaSize:min=128k,preferred=512k,wasteLimit=128k
[ERROR] Parse error in -XXtlasize arguments: Unknown parameter wasteLimit
Could not create the Java virtual machine.

Posted by guest on August 19, 2013 at 08:50 PM PDT #

You cannot apply this in JRockit R27 version. Make you use JRockit version R28.1 or above.

Posted by Ahmed on August 20, 2013 at 12:14 PM PDT #


EPM Planning

Current JVM Heap Size Parameters

USER_MEM_ARGS="-Xms27648m -XX:PermSize=64m -XX:MaxPermSize=256m -Xmx27648m -XXaggressive -XXgcThreads=4 -XXcompressedRefs:size=32GB -XXtlasize:min=32k,preferred=256k,wasteLimit=32k"

<Apr 17, 2014 9:30:29 AM EDT> <Error> <Server> <esu2e104.federated.fds> <Planning0> <DynamicListenThread[Default]> <<WLS Kernel>> <> <> <1397741429523> <BEA-002608> <The ListenThread because of an error: java.lang.OutOfMemoryError

java.lang.OutOfMemoryError: getNewTla.
java.lang.OutOfMemoryError: getNewTla

We also Tried below settings but same results.

Jagdish Ghatge

Posted by guest on April 18, 2014 at 08:05 AM PDT #


It seems like you are using switches from Sun JVM as well as from JRockit combined. For JRockit R28.x you only need following switches and remove rest of the switches.:

-Xms1024m -Xmx4096m -XXcompressedRefs:size=32GB -XXtlaSize:min=128k,preferred=512k,wasteLimit=128k

Thanks. - Ahmed (CEAL)

Posted by Ahmed on April 20, 2014 at 04:38 PM PDT #


Still have issues with TLA. Find below error log from planning. Seeing new thing "maximum thread constraint ASYNC_REP_FLUSH_WM is reached"

####<May 14, 2014 8:49:13 AM EST> <Info> <WorkManager> <esu2e101.federated.fds> <Planning0> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1400075353847> < > <maximum thread constraint ASYNC_REP_FLUSH_WM is reached>
####<May 14, 2014 8:51:05 AM EST> <Error> <Kernel> <esu2e101.federated.fds> <Planning0> <[STANDBY] ExecuteThread: '24' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1400075465667> <BEA-000802> <ExecuteRequest failed
java.lang.OutOfMemoryError: getNewTla.
java.lang.OutOfMemoryError: getNewTla
at weblogic.diagnostics.logging.LogVariablesImpl.getLogVariablesResolver(

Jagdish Ghatge

Posted by guest on May 14, 2014 at 11:28 AM PDT #


We are running Siebel 8.1 with BIP. Server has 24G memory, latest Kernel, 8G memory for BIP and the JRockit is as your recommendation and it still crash after few hours of re-bounced.

jrockit-jdk1.6.0_37-R28.2.5-4.1.0/bin/java -jrockit -Xms8196m -Xmx8196m -XXtlaSize:min=128k,preferred=512k,wasteLimit=128k

Any hint is highly appreciated.

Posted by Steve Nguyen on October 23, 2014 at 01:40 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed