SNOW-1408151: net.snowflake.client.core.SFException: JDBC driver internal error: unexpected exception java.lang.NullPointerExceptionnull.

[IRus]

1. What version of JDBC driver are you using?
   3.14.0

2. What operating system and processor architecture are you using?
   Amazon Linux 2

3. What version of Java are you using?
   Corretto 17

4. What did you do?
   No changes on app side

5. What did you expect to see?
   No exceptions in logs.

6. Can you set logging to DEBUG and collect the logs?

   https://community.snowflake.com/s/article/How-to-generate-log-file-on-Snowflake-connectors

7. What is your Snowflake account identifier, if any? (Optional)

Exception

heartbeat error - message=JDBC driver internal error: unexpected exception java.lang.NullPointerException: Cannot read field "name" because "x0" is null at net.snowflake.client.jdbc.telemetryOOB.TelemetryService$TELEMETRY_SERVER_DEPLOYMENT.access$000(TelemetryService.java:270).

net.snowflake.client.core.SFException: JDBC driver internal error: unexpected exception java.lang.NullPointerExceptionnull.
    at net.snowflake.client.core.SFSession.heartbeat(SFSession.java:865)
    at net.snowflake.client.core.HeartbeatBackground.run(HeartbeatBackground.java:192)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
    at java.util.concurrent.FutureTask.run(FutureTask.java:264)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
    at java.lang.Thread.run(Thread.java:840)

[sfc-gh-wfateem]

Hi @IRus,

This issue you're seeing was addressed in PR #1608 and that was fixed starting with version 3.14.4. Can you upgrade the JDBC driver and check if that addresses the issue, please?

[sfc-gh-wfateem]

Hey @IRus,

I'm just checking in to see if you were able to confirm that the newer JDBC driver releases starting with 3.14.4 address this problem.

[IRus]

@sfc-gh-wfateem Hi, I apologize for the delay, we were doing testing with new driver version.
Now it's deployed to production and the issue disappeared, thank you!