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.

Bug 172807 - [72cat][69cat][68cat] AWT thread blocked for 10786 ms.
Summary: [72cat][69cat][68cat] AWT thread blocked for 10786 ms.
Status: RESOLVED DUPLICATE of bug 221602
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Libor Fischmeistr
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-22 18:55 UTC by Michel Graciano
Modified: 2014-10-06 22:13 UTC (History)
11 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 158879

Attachments
nps snapshot (256.00 KB, application/nps)
2009-11-17 08:35 UTC, Eduardo.m Costa 		Details
nps snapshot (256.00 KB, application/nps)
2010-02-07 15:47 UTC, Exceptions Reporter 		Details
nps snapshot (256.00 KB, application/nps)
2010-02-11 12:43 UTC, Exceptions Reporter 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michel Graciano 2009-09-22 18:55:23 UTC 
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
Comment 1 Eduardo.m Costa 2009-11-17 08:35:58 UTC 
Created attachment 91181 [details]
nps snapshot
Comment 2 Exceptions Reporter 2010-02-07 15:47:50 UTC 
Created attachment 93944 [details]
nps snapshot
Comment 3 Exceptions Reporter 2010-02-11 12:43:42 UTC 
Created attachment 94097 [details]
nps snapshot

Running a SQL Query
Comment 4 Jiri Rechtacek 2010-10-15 14:21:03 UTC 
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.
Comment 5 Michel Graciano 2012-04-05 19:45:28 UTC 
I think it should be fixed some way, maybe WONTFIX?
Comment 6 matthias42 2014-10-06 22:13:28 UTC 
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 ***