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: | AssertionError: Accessing remote host. Do not call in awt | ||
---|---|---|---|
Product: | connecteddeveloper | Reporter: | Jaromir Uhrik <juhrik> |
Component: | Jira | Assignee: | Tomas Stupka <tstupka> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | CC: | mmirilovic |
Priority: | P1 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://statistics.netbeans.org/exceptions/detail.do?id=151080 | ||
Issue Type: | DEFECT | Exception Reporter: | 151080 |
Attachments: |
stacktrace
Attaching messages.log |
Description
Jaromir Uhrik
2009-05-13 12:46:34 UTC
Created attachment 82043 [details]
stacktrace
I was not able to get rid of exception dialog - it appeared again and again so that I needed to kill NetBeans. Increasing the priority to P1. Created attachment 82045 [details]
Attaching messages.log
cdev #a1cb23ee7d08 I am not sure if this is the final fix but it certainly solves some scenarios: The assert prevented a repository configuration to be loaded from the server but also prevented loading from the CACHE. I moved the assert to the point when the configuration is really being loaded from a remote host. One of reproduced scenarios: 1) Login to Kenai 2) Open Team->Find issues 3) Search for issues under a kenai project and wait for the search to finish 4) Logout from kenai 4 - this will set the configuration field in the repository to null and the AWT will force the configuration command haven't seen this for some time - fixed Verified. I have the same experience - last time it didn't appear. |