This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Build: NetBeans IDE Dev (Build 091012) VM: Java HotSpot(TM) Client VM, 14.0-b16, Java(TM) SE Runtime Environment, 1.6.0_14-b08 OS: SunOS, 5.10, x86 Stacktrace: org.h2.jdbc.JdbcSQLException: The object is already closed [90007-79] at org.h2.message.Message.getSQLException(Message.java:103) at org.h2.message.Message.getSQLException(Message.java:114) at org.h2.message.Message.getSQLException(Message.java:77) at org.h2.message.Message.getSQLException(Message.java:149) at org.h2.jdbc.JdbcConnection.checkClosed(JdbcConnection.java:1280) at org.h2.jdbc.JdbcStatement.checkClosed(JdbcStatement.java:833)
Created attachment 89436 [details] stacktrace
The first exception in a sequence of "object is already closed" was: (but it doesn't explain what really happened) org.h2.jdbc.JdbcSQLException: Statement was canceled or the session timed out; SQL statement: SELECT thread_id, MAX(time_stamp) FROM CallStack WHERE thread_id IN (1) AND 0 <= time_stamp AND time_stamp <= 58524226647 GROUP BY thread_id [90051-79] at org.h2.message.Message.getSQLException(h2-1.0.79.jar:103) at org.h2.message.Message.getSQLException(h2-1.0.79.jar:114) at org.h2.message.Message.getSQLException(h2-1.0.79.jar:77) at org.h2.message.Message.getSQLException(h2-1.0.79.jar:149) at org.h2.command.Command.checkCanceled(h2-1.0.79.jar:166) at org.h2.command.Prepared.checkCanceled(h2-1.0.79.jar:268) at org.h2.command.dml.Select.queryGroup(h2-1.0.79.jar:293) at org.h2.command.dml.Select.queryWithoutCache(h2-1.0.79.jar:542) at org.h2.command.dml.Query.query(h2-1.0.79.jar:233) at org.h2.command.CommandContainer.query(h2-1.0.79.jar:79) at org.h2.command.Command.executeQueryLocal(h2-1.0.79.jar:140) at org.h2.command.Command.executeQuery(h2-1.0.79.jar:121) at org.h2.jdbc.JdbcStatement.executeQuery(h2-1.0.79.jar:75) at org.netbeans.modules.dlight.impl.SQLDataStorage.select(org-netbeans-modules-dlight.jar:463) at org.netbeans.modules.dlight.core.stack.storage.impl.SQLStackDataStorage.getThreadSnapshots(org-netbeans-modules-dlight-core-stack.jar:600) at org.netbeans.modules.dlight.core.stack.storage.impl.SQLStackDataStorage._getThreadDump(org-netbeans-modules-dlight-core-stack.jar:692) at org.netbeans.modules.dlight.core.stack.storage.impl.SQLStackDataStorage.getThreadDump(org-netbeans-modules-dlight-core-stack.jar:622) at org.netbeans.modules.dlight.threadmap.dataprovider.ThreadMapDataProviderImpl.getThreadDump(org-netbeans-modules-dlight-threadmap-support.jar:227) at org.netbeans.modules.dlight.visualizers.threadmap.ThreadMapVisualizer$1$1.run(org-netbeans-modules-dlight-visualizers.jar:120) at org.netbeans.modules.dlight.util.DLightExecutorService$2.run(org-netbeans-modules-dlight-util.jar:89) at org.openide.util.RequestProcessor$Task.run(org-openide-util.jar:602) at org.openide.util.RequestProcessor$Processor.run(org-openide-util.jar:1084)
It is still not clear what happened and how to reproduce the situation. Marking INCOMPLETE. I've added more logging and done some cleanup of database access logic: http://hg.netbeans.org/cnd-main/rev/293fc84d460f . Hope it will help to track down the bug later.
Created attachment 90593 [details] stacktrace
Created attachment 91396 [details] stacktrace
I have tested profiling demo with extended dtrace provider. Exception was when I clicked on thread map.
Should check if it is reproducible in the current release
let's evaluate exceptions as P2 issues
I cannot reproduce the problem. Close as works for me