|
|
# Possible reasons:
2 q& b$ z: t, w' v0 r+ g+ v; R3 V2 L u# The system is out of physical RAM or swap space+ W0 M6 K z. b" Q
# The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap+ f8 {7 A9 k+ c9 O. u% j0 J! V$ ?
# Possible solutions:
# ]9 K0 Q! L% h9 h# Reduce memory load on the system
2 {% w* L# I4 P j# Increase physical memory or swap space7 t/ O: V# a4 w* W+ [9 R
# Check if swap backing store is full
0 k. M3 @9 K! B# Decrease Java heap size (-Xmx/-Xms)8 r6 H& A4 G5 `9 L' F
# Decrease number of Java threads
0 D' g6 h. B' K" M# Decrease Java thread stack sizes (-Xss)
; x/ J" ~8 P6 J; p# Set larger code cache with -XX:ReservedCodeCacheSize=
) o2 ^. W1 k1 h9 E" l# JVM is running with Zero Based Compressed Oops mode in which the Java heap is) x2 x* d8 b7 x6 c
# placed in the first 32GB address space. The Java Heap base address is the
5 q1 v. {+ b" A) S- b& a ~5 [& J3 `# maximum limit for the native heap growth. Please use -XX:HeapBaseMinAddress
, Z) w1 p. ~( v: u# to set the Java Heap base and to place the Java Heap above 32GB virtual address.
1 x2 ?2 p! I) d8 V( S- _5 j$ s; f把所有其他程序关掉,增加jvm内存分配 |
|
Snapsnap
2023-2-3 16:19:17
楼主