[
https://issues.apache.org/jira/browse/NETBEANS-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16464326#comment-16464326
]
Sven Reimers commented on NETBEANS-620:
---------------------------------------
Further details. It seems that the problem is that in JdbcGraphBuilder line 417
{code:java}
ClassRepository.lookupClass(STATEMENT_INTERFACE, 0){code}
is called but the original detected super interface for the loaded subclass was
in
{code:java}
ClassRepository.lookupClass(STATEMENT_INTERFACE, 2){code}
So it seems that with 10 (or 9 did not try this out) there is not only
classLoaderId 0 but in my sample at least up to id 2 ..
Anyone able to explain? Will keep digging.
> profiling SQL queries doesn't work under JDK 10
> -----------------------------------------------
>
> Key: NETBEANS-620
> URL: https://issues.apache.org/jira/browse/NETBEANS-620
> Project: NetBeans
> Issue Type: Bug
> Components: profiler - Base
> Affects Versions: 9.0
> Environment: I tested under NetBeans 9.0 build 395 with a project
> that uses a Postgres database.
> Reporter: Glenn Holmer
> Priority: Blocker
> Labels: BLOCKER
>
> Profiler's SQL query profiling feature does not work under JDK 10:
> 1) Create or open a project that uses JDBC queries to a database.
> 2) Click the profiler icon in the toolbar.
> 3) In the Profiler button dropdown, select "SQL Queries".
> 4) Click the gear icon at the right of the profiler toolbar and select "All
> queries".
> 5) Click the "Profile" button to start profiling.
> The program runs, but no SQL query data are returned. This works fine under
> JDK 8.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
