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 164591 - [67cat] IDE deadlocks after connection error
Summary: [67cat] IDE deadlocks after connection error
Status: RESOLVED DUPLICATE of bug 155786
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-06 14:28 UTC by misterm
Modified: 2009-05-12 16:52 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Thread dump (12.18 KB, text/plain)
2009-05-06 14:31 UTC, misterm
Details
messages.log (6.64 MB, text/plain)
2009-05-06 14:34 UTC, misterm
Details

Note You need to log in before you can comment on or make changes to this bug.
Description misterm 2009-05-06 14:28:17 UTC
[ BUILD # : 6.7 beta ]
[ JDK VERSION : 1.6.* ]

While trying to execute some statements on a connection that was
reset due to network issues, the IDE displays a dialog saying it
cannot use the connection. The dialog cannot be closed and the IDE
becomes frozen.
Comment 1 misterm 2009-05-06 14:31:03 UTC
Created attachment 81649 [details]
Thread dump
Comment 2 misterm 2009-05-06 14:34:57 UTC
Created attachment 81650 [details]
messages.log
Comment 3 Jiri Rechtacek 2009-05-11 09:53:45 UTC
There is no deadlock in the attached thread dump. While investing a messages.log I found out the original cause is
OutOfMemoryError thus it's unable to create new native thread to repair a broken db connection. I guess it's random case. 
Michael, are you able to reproduce it again? Thanks
Due to a random nature and the original cause belongs out of db module scope I decrease the priority to P3, I can only
fix that dialog won't block IDE in such a case.
Comment 4 Jiri Rechtacek 2009-05-12 16:52:53 UTC

*** This issue has been marked as a duplicate of 155786 ***