NoClassDefFoundError: java/sql/Timestamp

[daschneider]

When trying to do JDBC profiling the process being profiled generates the following error (many times):

lang.NoClassDefFoundError - java/sql/Timestamp Details: java/sql/Timestamp
java.lang.NoClassDefFoundError: java/sql/Timestamp
at org.netbeans.lib.profiler.server.ProfilerRuntimeCPU.converToString(ProfilerRuntimeCPU.java:788) ~[?:?]
at org.netbeans.lib.profiler.server.ProfilerRuntimeCPU.addParameter(ProfilerRuntimeCPU.java:687) ~[?:?]
at com.zaxxer.hikari.pool.HikariProxyPreparedStatement.setTimestamp(HikariProxyPreparedStatement.java) ~[HikariCP-3.2.0.jar:?]

Steps to reproduce the behavior:
Perform a JDBC profile of an application that executes a lot of database statements.

Expected behavior
Should be able to generate a JDBC profile.

Desktop (please complete the following information):

• OS: Ubuntu server 18.04
• JDK version [11.0.1+13]
• Version [1.4.2]
• Database PostgreSQL 10.x

[thurka]

It looks like this is caused by JDK modularisation in JDK 9+. Can you try to run your application on JDK 8 instead of JDK 11?

[daschneider]

Unfortunately we can't run our app using Java 8. The app uses the new HTTP 2 client classes from Java 11 so it has to run with Java 11 or newer.

[thurka]

Unfortunately we can't run our app using Java 8. The app uses the new HTTP 2 client classes from Java 11 so it has to run with Java 11 or newer.

:-( Too bad.

[thurka]

Hopefully fixed in master.

[daschneider]

Thanks for the quick turn around :)

[mohitprasanth]

I am using 1.4.4 version, facing the same issue while running JDBC profiling.
Caused by: java.lang.NoClassDefFoundError: java/sql/Timestamp

[thurka]

I am using 1.4.4 version, facing the same issue while running JDBC profiling.
Caused by: java.lang.NoClassDefFoundError: java/sql/Timestamp

This is strange. Please file separate issue. Do not forget to attach messages.log and full exception. Thanks.

[airdrik]

I've run into this as well, and seeing that the code in question is in the Netbeans codebase, I went ahead and reported the issue upstream: https://issues.apache.org/jira/browse/NETBEANS-3318

[thurka]

I've run into this as well

Did you see it in VisualVM? It is fixed in VisualVM 1.4.3.

[airdrik]

My testing was using VisualVM 1.4.4, freshly downloaded.

Checking the code fix here, it looks like that only applies to profiling GraalVM processes, while I'm assuming the fix for regular JVM profiling requires the fix in the NetBeans profiler code.

[thurka]

No, it does not. From Java point of view, there is no difference between GraalVM and JVM.

Can you, please, post the stacktrace?