"Other" Allocation Reported By JRCMD print_memusage Is Too High And Causing An OutOfMemory Issue (Doc ID 2073773.1)

Last updated on FEBRUARY 11, 2017

Applies to:

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

Symptoms

The machine running the WebLogic instance is repeatedly running out of memory. By using jrcmd print_memusage, the "Other" allocation reported by that command seems to be too high. The snapshots below show Other has grown from 0.5 to 6 GB.

Memory usage immediately after restart:
--------------------------------------
Total mapped 14,880,200KB (reserved=2967844KB)
- Java heap 10485760KB (reserved=1793696KB)
- GC tables 350732KB
- Thread stacks 70460KB (#threads=72)
- Compiled code 1048576KB (used=31243KB)
- Internal 1672KB
- OS 2125060KB
- Other 592,116KB
- Classblocks 10112KB (malloced=9999KB #26907)
- Java class data 194688KB (malloced=194393KB #122908 in 26907 classes)
- Native memory tracking 1024KB (malloced=113KB #10)

Memory usage after some time:
-----------------------------------------
Total mapped 20,227,820KB (reserved=1163348KB)
- Java heap 10485760KB (reserved=21200KB)
- GC tables 186888KB
- Thread stacks 70460KB (#threads=72)
- Compiled code 1048576KB (used=33927KB)
- Internal 1864KB
- OS 2125060KB
- Other 6,101,340KB
- Classblocks 10112KB (malloced=9976KB #26773)
- Java class data 196736KB (malloced=195632KB #122211 in 26773 classes)
- Native memory tracking 1024KB (malloced=119KB #10)

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