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 200909220201) VM: Java HotSpot(TM) Client VM, 14.2-b01, Java(TM) SE Runtime Environment, 1.6.0_16-b01 OS: Linux, 2.6.28-15-generic, i386 User comments: Maximum slowness yet reported was 10786 ms, average is 7358
Created attachment 91181 [details] nps snapshot
Created attachment 93944 [details] nps snapshot
Created attachment 94097 [details] nps snapshot Running a SQL Query
The snapshot shared the same cause: detection if a database connection is opened or not, it means calling JDBC driver's implementation of isClosed() method. Seems that method might take too long time (e.g. oracle.jdbc.driver.PhysicalConnection.isClosed(), org.apache.derby.impl.jdbc.EmbedConnection.getWarnings(), oracle.jdbc.driver.OracleConnection.isClosed() etc.) No current plan to fix it. Needs change of architecture of DB tooling modules to rid of depending on these methods in AWT queues.
I think it should be fixed some way, maybe WONTFIX?
The patch from the referenced bug dispatches the check into a seperate Thread and limits the wait time to 1000ms. *** This bug has been marked as a duplicate of bug 221602 ***