OutofMemory on GetNEWTLA

Weblogic managed server failed sporadically with out of memory on TLA. After investigating the errors in the logs and research oracle forums I came to know that the Thread local Area ( TLA) value was set to default value 2KB , which was not sufficient hence we were encountering OOM on TLA.

For certain OS JVM handles the TLA  mem allocation dynamically but for some it is required to manually increase. This may require some experimentation as it is hard to say exactly how large you need this to be, you can slowly increase it until the error goes away.

Error:

####<Warning> <RMI> <[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <7b90471a4de3bc66:-511d663d:151a1e81621:-8000-000000000002f2bd> <1450407974931> <BEA-080004> <An error was thrown by rmi server: javax.management.remote.rmi.RMIConnectionImpl.queryNames(Ljavax.management.ObjectName;Ljava.rmi.MarshalledObject;Ljavax.security.auth.Subject;) 

java.lang.OutOfMemoryError: getNewTla. 

java.lang.OutOfMemoryError: getNewTla 

<Error> <RMI> <ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <> <b2ae77c08e5e739b:4d6de871:151889120ef:-8000-000000000002f0c8> <1449981645585> <BEA-080001> <Error in Dispatcher 

java.lang.OutOfMemoryError. 

java.lang.OutOfMemoryError 

####< <weblogic.cluster.MessageReceiver> <<WLS Kernel>> <> <b2ae77c08e5e739b:4d6de871:151889120ef:-8000-000000000002f0ca> <1449981646763> <BEA-003107> <Lost 1 unicast message(s).> 

####< <[ACTIVE] ExecuteThread: '25' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <b2ae77c08e5e739b:4d6de871:151889120ef:-8000-000000000002f0cb> <1449981649184> <BEA-002634> <The server "AdminServer" disconnected from this server.> 

Script: "setDomain.sh" : JAVA_OPTIONS="${JAVA_OPTIONS} ${JAVA_PROPERTIES} -Dwlw.iterativeDev=${iterativeDevFlag} -Dwlw.testConsole=${testConsoleFlag} -Dwlw.logErrorsToConsole=${logErrorsToConsoleFlag} -XXtlasize:min=8k,preferred=512k"
export JAVA_OPTIONS


***Use this option with caution, as changing the thread-local area size can have severe impact on performance.***

Specify <size> in bytes, using the normal K,M,G suffixes.

For example:
-XXtlasize:min=8k,preferred=512k
sets a TLA size suitable for heaps of several GB.

***Note: The old style of setting TLA size (that is, -XXtlasize=256k) is still supported but has been deprecated. If you use the old style, JRockit JVM will interpret the option as if the fixed parameter was used; for example, -XXtlasize=256k would be interpreted as -XXtlasize:fixed=256k.

Reference:
http://docs.oracle.com/cd/E13150_01/jrockit_jvm/jrockit/jrdocs/refman/optionXX.html