The Snowflake JDBC driver v3.19.0 encounters an error for Java due to change in encapsulation method after JDK V16.
While checking internal logs using below SPL:
SPL:
index=_internal sourcetype=*dbx* *ERROR*
ERRORs:
2025-04-18 09:15:24.135 +0000 Trace-Id=4123344_xyz [Scheduled-Job-Executor-0] ERROR com.zaxxer.hikari.pool.HikariPool - unnamed_pool_857660320_jdbc__snowflake__//uo10923.eu-central-1.snowflakeco
mputing.com/?user__gl_app_soc&db_SNOWFLAKE&role_ AUDITOR&application__SPLUNK&insecureMode_true Error thrown while acquiring connection from data source net.snowflake.client.jdbc.SnowflakeSQLException: JDBC driver internal error: exception creating result java.lang.ExceptionInInitializerError at net.snowflake.client.jdbc.internal.apache.arrow.memory.unsafe. UnsafeAllocat
IonManager.<clinit>(UnsafeAllocationManager.java:28).
at net.snowflake.client.jdbc.SnowflakeStatementV1.execute Internal (SnowflakeStatementV1.java:385)
at net.snowflake.client.jdbc.SnowflakeStatementV1.execute(SnowflakeStatement.V1.java:428)
at com.zaxxer.hikari.pool.PoolBase.executeSql (PoolBase.java: 583)
After further investigation, it was found that the issue occurs due to incompatibility between the Snowflake JDBC driver(v3.19.0) and JDK 16 or later versions.
The driver attempts to use Java Reflection to access a private member of the `java.nio.Buffer` class. While this was permitted in earlier versions of Java, strong encapsulation was enforced by default starting with JDK 16, which restricts reflective access to internal JDK classes and private members unless explicitly allowed.
As a result, the driver’s reflective operations are blocked, causing the error.
To resolve this issue, please add the following JVM argument in the "Apps > Splunk DB Connect > Configuration > Settings" page under JVM Options:
JVM Argument: --add-opens java.base/java.nio=ALL-UNNAMED
This will allow the Snowflake JDBC driver to access the required internal class members at runtime, bypassing the strong encapsulation restriction introduced in JDK 16 and above.
Snowflake Driver Incompatibility issue
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
01-Oct-2026
|
Initial Release |