JavaGateway fails to start in zabbix-docker after upgrading 6.2 to 6.4

[Shurman]

Hi everyone!

So, the topic clearly states what is the problem.
I have a zabbix-docker environment, not very big, running 6.2.7 CentOS images.
There are no specific settings for Java in .env files

I checked out branch 6.2 of zabbix-docker and built Centos images myself with the latest tag (with the provided build.sh) - I have to store them in our local registry.
After that I changed 6.2.7 to 6.4.1 in my docker-compose.yml

Then I just start it normally. (aside: DB upgrade failed, I had to run "alter table media_type row_format = dynamic;" for it to pass)

Now, JavaGateway fails to start with OutOfMemory exception.

I do not see any specific setting for JVM - in settings and in the JVM arguments string recorded in the exception.

Any clues/directions?

I had to rollback the DB and version, so unfortunately I am unable to provide exact logs currently. :-( However if anyone is interested - I probably could.

[Shurman]

** Preparing Zabbix Java Gateway
** Preparing Zabbix Java Gateway log configuration file
Updating /etc/zabbix/zabbix_java_gateway_logback.xml 'DebugLevel' parameter: 'info'... updated
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Cannot create GC thread. Out of system resources.
# An error report file with more information is saved as:
# /usr/sbin/zabbix_java/hs_err_pid1.log
** Preparing Zabbix Java Gateway
** Preparing Zabbix Java Gateway log configuration file
Updating /etc/zabbix/zabbix_java_gateway_logback.xml 'DebugLevel' parameter: 'info'... updated
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Cannot create GC thread. Out of system resources.
# An error report file with more information is saved as:
# /tmp/hs_err_pid1.log
** Preparing Zabbix Java Gateway
** Preparing Zabbix Java Gateway log configuration file
Updating /etc/zabbix/zabbix_java_gateway_logback.xml 'DebugLevel' parameter: 'info'... updated
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Cannot create GC thread. Out of system resources.
# Can not save log file, dump to screen..
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Cannot create GC thread. Out of system resources.
# Possible reasons:
# The system is out of physical RAM or swap space
# The process is running with CompressedOops enabled, and the Java Heap may be blocking the growth of the native heap
# Possible solutions:
# Reduce memory load on the system
# Increase physical memory or swap space
# Check if swap backing store is full
# Decrease Java heap size (-Xmx/-Xms)
# Decrease number of Java threads
# Decrease Java thread stack sizes (-Xss)
# Set larger code cache with -XX:ReservedCodeCacheSize=
# This output file may be truncated or incomplete.
#
# Out of Memory Error (gcTaskThread.cpp:48), pid=1, tid=0x00007fb5f4de3740
#
# JRE version: (8.0_362-b09) (build )
# Java VM: OpenJDK 64-Bit Server VM (25.362-b09 mixed mode linux-amd64 compressed oops)
# Core dump written. Default location: /usr/sbin/zabbix_java/core or core.1
#
--------------- T H R E A D ---------------
Current thread (0x00005605e259c800): JavaThread "Unknown thread" [_thread_in_vm, id=1, stack(0x00007ffc08cea000,0x00007ffc08dea000)]
Stack: [0x00007ffc08cea000,0x00007ffc08dea000], sp=0x00007ffc08de3cb0, free space=999k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [libjvm.so+0xbed127] VMError::report_and_die()+0x247
V [libjvm.so+0x50e7cf] report_vm_out_of_memory(char const*, int, unsigned long, VMErrorType, char const*)+0x9f
V [libjvm.so+0x5e9d7f] GCTaskThread::GCTaskThread(GCTaskManager*, unsigned int, unsigned int)+0x16f
V [libjvm.so+0x5e9467] GCTaskManager::initialize()+0x307
V [libjvm.so+0x9f13d2] ParallelScavengeHeap::initialize()+0x3b2
V [libjvm.so+0xbb0e21] Universe::initialize_heap()+0x1b1
V [libjvm.so+0xbb10c6] universe_init()+0x46
V [libjvm.so+0x66341f] init_globals()+0x6f
V [libjvm.so+0xb8fd90] Threads::create_vm(JavaVMInitArgs*, bool*)+0x1f0
V [libjvm.so+0x751363] JNI_CreateJavaVM+0x63
C [libjli.so+0x953a] JavaMain+0x9a
C [libjli.so+0xeaec] ContinueInNewThread0+0x6c
C [libjli.so+0xb02b] ContinueInNewThread+0x7b
C [libjli.so+0xc3ec] JLI_Launch+0x123c
C [java+0x10b5] main+0x45
C [libc.so.6+0x3feb0] __libc_start_call_main+0x80
--------------- P R O C E S S ---------------
Java Threads: ( => current thread )
Other Threads:
=>0x00005605e259c800 (exited) JavaThread "Unknown thread" [_thread_in_vm, id=1, stack(0x00007ffc08cea000,0x00007ffc08dea000)]
VM state:not at safepoint (not fully initialized)
VM Mutex/Monitor currently owned by a thread: None
heap address: 0x00000000c4c00000, size: 948 MB, Compressed Oops mode: Non-zero based:0x00000000c4bff000
Narrow klass base: 0x0000000000000000, Narrow klass shift: 0
GC Heap History (0 events):
No events
Deoptimization events (0 events):
No events
Classes redefined (0 events):
No events
Internal exceptions (0 events):
No events
Events (0 events):
No events