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 231730 - IllegalThreadStateException: Should never be called from AWT thread
Summary: IllegalThreadStateException: Should never be called from AWT thread
Status: RESOLVED DUPLICATE of bug 225585
Alias: None
Product: cnd
Classification: Unclassified
Component: D-Light (show other bugs)
Version: 7.3
Hardware: All All
: P3 normal (vote)
Assignee: Maria Tishkova
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-24 15:35 UTC by Exceptions Reporter
Modified: 2015-09-25 21:26 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 201650

Attachments
stacktrace (1.50 KB, text/plain)
2013-06-24 15:35 UTC, Exceptions Reporter 		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 Exceptions Reporter 2013-06-24 15:35:16 UTC 
This bug was originally marked as duplicate of bug 225585, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE 7.3 (Build 201306052037)
VM: Java HotSpot(TM) 64-Bit Server VM, 23.7-b01, Java(TM) SE Runtime Environment, 1.7.0_17-b02
OS: Windows 7

User Comments:
GUEST: I had C++ runing on remote masine. 
And had a disconnect.




Stacktrace: 
java.lang.IllegalThreadStateException: Should never be called from AWT thread
   at org.netbeans.modules.nativeexecution.api.util.ConnectionManager.connectTo(ConnectionManager.java:321)
   at org.netbeans.modules.nativeexecution.api.NativeProcessBuilder$1.confirmed(NativeProcessBuilder.java:193)
   at org.netbeans.core.NbErrorManager$Exc.confirm(NbErrorManager.java:278)
   at org.netbeans.core.NotifyExcPanel$2.run(NotifyExcPanel.java:300)
   at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:251)
   at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:727)
Comment 1 Exceptions Reporter 2013-06-24 15:35:17 UTC 
Created attachment 136232 [details]
stacktrace
Comment 2 Vladimir Kvashin 2015-09-25 21:26:06 UTC 
Yes, it is a duplicate of issue 225585, it was just fixed a little bit late to get into release 7.3

*** This bug has been marked as a duplicate of bug 225585 ***