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.
Build: NetBeans IDE Dev (Build 090513) VM: Java HotSpot(TM) Client VM, 1.5.0_16-133, Java(TM) 2 Runtime Environment, Standard Edition, 1.5.0_16-b06-284 OS: Mac OS X, 10.5.6, i386 User Comments: juhrik: Opened javaapplication13 from testkenai. Then clicked on "all issues" link of this project in Kenai dashboard and the exception appeared. Stacktrace: java.lang.AssertionError: Accessing remote host. Do not call in awt at org.netbeans.modules.jira.repository.JiraRepository.getConfigurationIntern(JiraRepository.java:381) at org.netbeans.modules.jira.repository.JiraRepository.getConfiguration(JiraRepository.java:371) at org.netbeans.modules.jira.issue.NbJiraIssue.getType(NbJiraIssue.java:239) at org.netbeans.modules.jira.issue.JiraIssueNode$TypeProperty.getValue(JiraIssueNode.java:123) at org.netbeans.modules.jira.issue.JiraIssueNode$TypeProperty.getValue(JiraIssueNode.java:115) at org.netbeans.modules.bugtracking.ui.issuetable.IssueTable$CellRenderer.getTableCellRendererComponent(IssueTable.java:388)
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.