|
|
# Possible reasons:! X# U: C7 T: F& j4 M8 O5 l; o
# The system is out of physical RAM or swap space& U& w" f2 C) Z- u5 a4 b7 `
# The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap# L& o5 e! K) d; C7 s. H% @
# Possible solutions:% o; y9 S! T( @- @8 r
# Reduce memory load on the system9 Y3 { `3 s/ X- b' H4 j t
# Increase physical memory or swap space6 k" j* l- `0 R G W- U/ J" r
# Check if swap backing store is full8 t. S2 ^3 a* f9 w
# Decrease Java heap size (-Xmx/-Xms)
+ I v6 y2 x) w' M4 u# Decrease number of Java threads
0 b$ `% e% a1 U4 I# Decrease Java thread stack sizes (-Xss)3 U* O% | E" n% h" x- E
# Set larger code cache with -XX:ReservedCodeCacheSize=
% T( [# B2 k4 ]% }' I4 c' U3 k# JVM is running with Zero Based Compressed Oops mode in which the Java heap is0 S) g9 v. B# u7 E' ~+ t% Y; F# ?
# placed in the first 32GB address space. The Java Heap base address is the$ t) T' E, @$ U* ~- a- ^
# maximum limit for the native heap growth. Please use -XX:HeapBaseMinAddress& t) h; b7 i( }" F* s) |8 q
# to set the Java Heap base and to place the Java Heap above 32GB virtual address.3 g8 b% @, `( Z* l
把所有其他程序关掉,增加jvm内存分配 |
|
Snapsnap
2023-2-3 16:19:17
楼主