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.
The thread is blocked on close window till the execution of a sql command is finished. The thread stack trace is in attachment.
Created attachment 12070 [details] AWT-EventQueue stack trace
Could you describe it more, please? I don't understand what do you mean.
I haven't got more info. Closing as INVALID. Feel free to reopen with more descriprive comments.
It was some extreme use case. The data is runned on the another continent :-) verified
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.
I think it is not so serious issue for users. I am lowering priority to P3.
Created attachment 13216 [details] threads dump
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.
Changing back the priority. I increased it by accideng with my previous comment.
*** Issue 41387 has been marked as a duplicate of this issue. ***
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?
Created attachment 17133 [details] threads dump
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.
can't see any blocked GUI when SQL is performing in current DEV (4.0) builds
Target milestone changed from 4.1 to 4.0