Expert Advice

JVM_MEM31Free_Warning  
Situation Description
Suggested Actions
Situation Description

The warning threshold for free 31-bit memory has been breached.

 

Possible Causes
  1. Native memory leak.
  2. For 31-bit JVMs, the maximum heap size is too large.
  3. Too many threads in the application.
  4. Native memory leak in JNI code.
  5. Large amounts of authorized storage allocated.
  6. Other programs in the address space are consuming memory.

 

Suggested Actions
  1. Continue to monitor the JVM memory to see if the condition is worsening.
  2. Examine Health history to see if the number of threads is growing.
  3. If Garbage Collection rates are low, consider lowering the minimum Java heap size.
  4. Check the address space memory usage of authorized memory in LSQA/SWA/229/230.

 

Copyright IBM Corp. 2019 All Rights Reserved US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contact IBM