|
The warning threshold for free 31-bit memory has been breached.
|
- Native memory leak.
- For 31-bit JVMs, the maximum heap size is too large.
- Too many threads in the application.
- Native memory leak in JNI code.
- Large amounts of authorized storage allocated.
- Other programs in the address space are consuming memory.
|
- Continue to monitor the JVM memory to see if the condition is worsening.
- Examine Health history to see if the number of threads is growing.
- If Garbage Collection rates are low, consider lowering the minimum Java heap size.
- 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
|
|
|