Standalone Java client using wlfullclient.jar running into OOM (Doc ID 2194362.1)

Last updated on DECEMBER 27, 2016

Applies to:

Oracle WebLogic Server - Version 12.1.2.0.0 and later
Information in this document applies to any platform.

Symptoms

Memory leak is observed in weblogic.kernel.ResettableThreadLocal$ThreadStorage .

A standalone client application using wlfullclient.jar with java.naming.factory.url.pkgs in the environment is facing OutofMemory error . A simple application that simulated the issue binds a string starting with java.global and makes 5K lookup. The heapdump captured on the client process shows 5K+ instances of AuthenticatedSubject instances .

The thread java.lang.Thread @ 0xc0148c60 pool-1-thread-2 keeps local variables with total size 614,004,520 (93.01%) bytes.

The memory is accumulated in one instance of "java.lang.Object[]" loaded by "<system class loader>".Keywords
java.lang.Object[]

 

Cause

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