This discussion is archived
1 Reply Latest reply: Apr 17, 2013 5:58 AM by 997468 RSS

java.lang.OutOfMemoryError: getNewTla

JCGO Newbie
Currently Being Moderated
Hi All,

We have a single instance 10.3.5 WLS server that has gone down with the following error:

Error> <RMI> <BEA-080001> <Error in Dispatcher
java.lang.OutOfMemoryError: getNewTla.
java.lang.OutOfMemoryError: getNewTla
     at weblogic.rmi.internal.wls.WLSRMIEnvironment.createExecuteRequest(
     at weblogic.rmi.internal.BasicServerRef.dispatch(
     at weblogic.rmi.internal.BasicServerRef.dispatch(
     at weblogic.rjvm.RJVMImpl.dispatchRequest(
     at weblogic.rjvm.RJVMImpl.dispatch(
     Truncated. see log file for complete stacktrace
HealthMonitor executing OMS thread dump at Apr 4, 2013 9:00:43 AM
"DefaultQuartzScheduler_Worker-3" prio=5 Thread id=76 TIMED_WAITING
     java.lang.Object.wait(Native Method)

"DynamicSSLListenThread[DefaultSecure]" daemon prio=9 Thread id=96 RUNNABLE Method)



JAVA Memory arguments: -Xms1024m -Xmx2048m -XX:CompileThreshold=8000 -XX:PermSize=1024m -XX:MaxPermSize=2048m

Using Jrockit....

I read some articles to set the this


any thoughts?

  • 1. Re: java.lang.OutOfMemoryError: getNewTla
    997468 Explorer
    Currently Being Moderated

    Did you tried using the java options - "-XXtlasize:min=8k,preferred=128k" ?
    The Thread Local Area (TLA) is the memory aread allocated to threads for storing local object allocation and is allocated from the heap space configured.

    As default value of TLA will vary with jrockit versions, you will have to try and test configuration required by your application.
    Refer to for more details.

    Also at time of OOM capture the heap details to check what is the consumption of heap at that point as a whole.


    Edited by: Ranjan K on Apr 17, 2013 5:58 AM


  • Correct Answers - 10 points
  • Helpful Answers - 5 points