java.lang.OutOfMemoryError: nativeGetNewTLA (Doc ID 1280728.1)

Last updated on JUNE 11, 2017

Applies to:

Oracle WebLogic Server - Version 8.1 to 10.0
Oracle WebLogic Server - Version 10.3.6 to 10.3.6
Information in this document applies to any platform.

Goal

Sometimes it is necessary to tune an environment when facing "java.lang.OutOfMemoryError: nativeGetNewTLA" errors.  For that, you can set some parameters of the Jrockit JVM to avoid those problems.

Exception example :

Weblogic launch this exception :

<BEA-100026> <An unexpected error was raised in HTTP session timeout callback, while checking session expiration.
java.lang.OutOfMemoryError: nativeGetNewTLA
at weblogic.servlet.internal.session.SessionContext.getIdsInternal(SessionContext.java:488)
at weblogic.servlet.internal.session.SessionContext$SessionInvalidator.cleanupExpiredSessions(SessionContext.java:924)
at weblogic.servlet.internal.session.SessionContext$SessionInvalidator.timerExpired(SessionContext.java:888)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>

 

Since JRockit version R27.3.1 and later, this is unnecessary in most situations as those version autotune.  But for older versions, you may need to tune some parameters for your needs.

 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms