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 37051 - AWT-EventQueue is blocked on close SQL command window
Summary: AWT-EventQueue is blocked on close SQL command window
Status: VERIFIED FIXED
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: PC Linux
: P2 blocker (vote)
Assignee: Radko Najman
URL:
Keywords: PERFORMANCE, THREAD
: 41387 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-11-05 12:53 UTC by pzajac
Modified: 2004-11-05 15:15 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
AWT-EventQueue stack trace (5.32 KB, text/plain)
2003-11-05 12:55 UTC, pzajac 		Details
threads dump (11.19 KB, text/plain)
2004-02-03 15:37 UTC, pzajac 		Details
threads dump (14.49 KB, text/plain)
2004-08-25 14:35 UTC, pzajac 		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 pzajac 2003-11-05 12:53:20 UTC 
The thread is blocked on close window till the
execution of a sql command is finished. The thread
stack trace is in attachment.
Comment 1 pzajac 2003-11-05 12:55:27 UTC 
Created attachment 12070 [details]
AWT-EventQueue stack trace
Comment 2 Radko Najman 2003-12-20 15:15:54 UTC 
Could you describe it more, please? I don't understand what do you mean.
Comment 3 Radko Najman 2004-01-19 13:48:32 UTC 
I haven't got more info. Closing as INVALID.
Feel free to reopen with more descriprive comments.
Comment 4 pzajac 2004-01-21 15:51:54 UTC 
It was some extreme use case. The data is runned on the another
continent :-) 
verified
Comment 5 pzajac 2004-02-03 10:32:02 UTC 
It some times occures when I am working with big oracle database. The
ide rests frezed. This doesn't like deadlock. The AWT-QUEUE is waiting
for a request preccessor. In the request proccessor are getted
metadata.  See to the thread dump.
Comment 6 Jiri Skrivanek 2004-02-03 15:10:31 UTC 
I think it is not so serious issue for users. I am lowering priority
to P3.
Comment 7 pzajac 2004-02-03 15:37:08 UTC 
Created attachment 13216 [details]
threads dump
Comment 8 Radko Najman 2004-02-03 16:00:20 UTC 
From the attached stack trace is visible that the problematic method
is getIndexInfo(). It is known problem of Oracle driver. This method
consumes a lot of time on tables with big number of rows.
Comment 9 Radko Najman 2004-02-03 16:02:59 UTC 
Changing back the priority. I increased it by accideng with my
previous comment.
Comment 10 Radko Najman 2004-08-13 09:44:18 UTC 
*** Issue 41387 has been marked as a duplicate of this issue. ***
Comment 11 pzajac 2004-08-25 14:34:01 UTC 
 I executed sql-command on bigger database (the query speds few
minutes).  After that I changed the document in the editor. The
awt-qeue was blocked. Are you sure that this is not so important Issue?
Comment 12 pzajac 2004-08-25 14:35:44 UTC 
Created attachment 17133 [details]
threads dump
Comment 13 Radko Najman 2004-09-02 13:40:08 UTC 
I implemented a workaround not to use Connection.isClosed() method.
Hopefully it can help. If not, feel free to reopen again.
I can't do anything with getIndexInfo() method. This is a performance
issue related to Oracle driver.
Comment 14 dmladek 2004-09-07 13:27:37 UTC 
can't see any blocked GUI when SQL is performing in current DEV (4.0)
builds
Comment 15 Radko Najman 2004-11-05 15:15:30 UTC 
Target milestone changed from 4.1 to 4.0