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.
Summary: | Forbid calling Keyring API in EQ | ||
---|---|---|---|
Product: | db | Reporter: | Petr Hejl <phejl> |
Component: | Code | Assignee: | Jiri Rechtacek <jrechtacek> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | jglick, kiran_pesse, mmirilovic, musilt2, sworisbreathing, tboudreau, tfruehbeck, tkhh, tzezula |
Priority: | P2 | Keywords: | RANDOM, THREAD |
Version: | 7.0 | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | thread dump as an attachment |
Description
Petr Hejl
2011-02-24 14:20:52 UTC
Created attachment 106411 [details]
thread dump as an attachment
I can reproduce it too. If I lock gnome-keyring-provider on my ubuntu then IDE freezes in New Entity Classes wizard. *** Bug 196048 has been marked as a duplicate of this bug. *** *** Bug 188624 has been marked as a duplicate of this bug. *** I don't have any patch yet that I'm satisfied with. I my point of view it's too risky to fix it close to CF, anyway. DatabaseConnection.getPassword when running in EQ could check whether this is locked. (Well, can't check a Java monitor, but can use java.util.concurrent equivalents.) If so, just return "" or something. Not great but much better than a deadlock. *** Bug 196620 has been marked as a duplicate of this bug. *** core-main/rev/4762e7ec74bf Integrated into 'main-golden', will be available in build *201104080400* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/4762e7ec74bf User: Jiri Rechtacek <jrechtacek@netbeans.org> Log: #195943: Forbid calling Keyring API in EQ *** Bug 195623 has been marked as a duplicate of this bug. *** *** Bug 207490 has been marked as a duplicate of this bug. *** |