We are trying to deploy on Java17 this time using the standard LOAD mechanism (till now we used extracted DDL for schema init).
As before (described in #347), we are using SQL_ASCII encoded DB and on the initialisation via LOAD we a gifted with VM crash, does it ring a bell?
client_encoding | SQL_ASCII
server_encoding | SQL_ASCII
WARNING: A command line option has enabled the Security Manager
WARNING: The Security Manager is deprecated and will be removed in a future release
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f1f63c8439e, pid=27113, tid=27113
#
# JRE version: OpenJDK Runtime Environment Temurin-17.0.5+8 (17.0.5+8) (build 17.0.5+8)
# Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.5+8 (17.0.5+8, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# V [libjvm.so+0x8b939e] jni_CallStaticObjectMethodV+0xae
#
# Core dump will be written. Default location: /DATA_PRIMARY/cores/%E_27113_%t.core
#
# An error report file with more information is saved as:
# /ZSSD/xz24/app/coord/hs_err_pid27113.log
#
# If you would like to submit a bug report, please visit:
# https://github.com/adoptium/adoptium-support/issues
#
WARNING: A command line option has enabled the Security Manager
WARNING: The Security Manager is deprecated and will be removed in a future release
java.nio.charset.UnsupportedCharsetException: X-PGSQL_ASCII
at java.base/java.nio.charset.Charset.forName(Charset.java:528)
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f1f63c8439e, pid=28005, tid=28005
#
# JRE version: OpenJDK Runtime Environment Temurin-17.0.5+8 (17.0.5+8) (build 17.0.5+8)
# Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.5+8 (17.0.5+8, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# V [libjvm.so+0x8b939e] jni_CallStaticObjectMethodV+0xae
#
# Core dump will be written. Default location: /DATA_PRIMARY/cores/%E_28005_%t.core
#
# An error report file with more information is saved as:
# /ZSSD/xz24/app/coord/hs_err_pid28005.log
#
# If you would like to submit a bug report, please visit:
Hello @jcflack!
We are trying to deploy on Java17 this time using the standard LOAD mechanism (till now we used extracted DDL for schema init).
As before (described in #347), we are using SQL_ASCII encoded DB and on the initialisation via LOAD we a gifted with VM crash, does it ring a bell?
From https://tada.github.io/pljava/use/charsets.html we assumed this should not be a problem (and had not been before java17)?
Also attaching the hs log.
hs_err_pid34733.log
Thanks!