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 37528 - IllegalStateException when executing CVS command
Summary: IllegalStateException when executing CVS command
Status: VERIFIED FIXED
Alias: None
Product: cnd
Classification: Unclassified
Component: Terminalemulator (show other bugs)
Version: 3.x
Hardware: PC Linux
: P2 blocker (vote)
Assignee: _ tboudreau
URL:
Keywords: API, THREAD
Depends on:
Blocks:
 
Reported: 2003-11-26 14:04 UTC by Jiri Skrivanek
Modified: 2008-12-23 08:36 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
stack trace (3.37 KB, text/plain)
2003-11-26 14:04 UTC, Jiri Skrivanek
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Skrivanek 2003-11-26 14:04:17 UTC
Exception is thrown during automated tests:

java.lang.IllegalStateException: This must happen
in the event thread!

Look at attached stack trace.
Tested on build 20031125-2031, JDK1.4.1_02-b06,
Linux 2.4.5.
Comment 1 Jiri Skrivanek 2003-11-26 14:04:43 UTC
Created attachment 12317 [details]
stack trace
Comment 2 Martin Entlicher 2003-11-26 14:51:36 UTC
Moving to core.
In the javadoc of IOProvider.getIO() there's nothing about that this
should be run in AWT.
The problem seems to be at org.netbeans.core.output.* which access the
UI.
Comment 3 Peter Zavadsky 2003-11-27 09:48:48 UTC
Well, it seems it should be that it needs to be called in AWT only.
Beside the actions there are also calls to winsys which are going to
be required to be called in AWT only.

On the other hand, this code seems to be older, please use the latest
build and provide actual stack trace.
Comment 4 Peter Zavadsky 2003-11-27 09:50:21 UTC
Yarda, what to do with this? Require the calls from AWT, or try to
make something in the core/output, but I don't know what yet.
Comment 5 _ tboudreau 2003-11-27 17:13:53 UTC
Okay, I've put a simple fix into OutputTabInner - it will now create
its popup menu lazily instead of doing it in the constructor.  I
*think* that will solve the problem, unless there's other stuff it's
doing in its constructor that shouldn't be done on the event thread.

Reopen if there's still a problem - I'm not quite sure how to
reproduce this.

Jelly will of course need to invoke the popup (if it does at all) from
the event thread, or you'll still see some exceptions.
Comment 6 Jiri Skrivanek 2003-12-15 18:54:51 UTC
Verified - exception never appeared again.
Comment 7 Quality Engineering 2008-12-23 08:36:27 UTC
moving terminal emulator issues to terminalemulator component.
To see the correct version and target milestone of this issue look at Issue
Activity table.