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 168808 - AssertionError: Accessing remote host. Do not call in awt
Summary: AssertionError: Accessing remote host. Do not call in awt
Status: RESOLVED WORKSFORME
Alias: None
Product: connecteddeveloper
Classification: Unclassified
Component: Jira (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jan Stola
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-20 13:15 UTC by Jaromir Uhrik
Modified: 2010-01-19 03:40 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 153921

Attachments
stacktrace (1.66 KB, text/plain)
2009-07-20 13:15 UTC, Jaromir Uhrik 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jaromir Uhrik 2009-07-20 13:15:14 UTC 
Build: NetBeans IDE Dev (Build 200907200201)
VM: Java HotSpot(TM) Client VM, 1.5.0_19-137, Java(TM) 2 Runtime Environment, Standard Edition, 1.5.0_19-b02-304
OS: Mac OS X, 10.5.7, i386

User Comments:
juhrik: In "my issues" list doubleclick on an issue line and the exception dialog appears...



Stacktrace: 
java.lang.AssertionError: Accessing remote host. Do not call in awt<br/>
        at org.netbeans.modules.jira.repository.JiraConfiguration.initProject(JiraConfiguration.java:373)<br/>
        at org.netbeans.modules.jira.repository.JiraConfiguration.ensureProjectLoaded(JiraConfiguration.java:350)<br/>
        at org.netbeans.modules.jira.repository.JiraConfiguration.getProjectById(JiraConfiguration.java:313)<br/>
        at org.netbeans.modules.jira.issue.IssuePanel.reloadForm(IssuePanel.java:375)<br/>
        at org.netbeans.modules.jira.issue.IssuePanel.setIssue(IssuePanel.java:170)<br/>
        at org.netbeans.modules.jira.issue.NbJiraIssue$Controller.<init>(NbJiraIssue.java:1234)<br/>
Comment 1 Jaromir Uhrik 2009-07-20 13:15:24 UTC 
Created attachment 84931 [details]
stacktrace
Comment 2 Jan Stola 2010-01-19 03:40:56 UTC 
I am not able to reproduce this issue and I believe that it should no longer occur => closing as non-reproducible. Feel free to reopen it if/when you are able to reproduce it but do not forget to describe exact steps to reproduce then. Thank you in advance.