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 76923 - IllegalStateException: getUrl called from AWT thread
Summary: IllegalStateException: getUrl called from AWT thread
Status: VERIFIED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-26 14:01 UTC by ehucka
Modified: 2007-01-11 17:30 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 ehucka 2006-05-26 14:01:37 UTC 
java.lang.IllegalStateException: getUrl called from AWT thread
        at 
org.netbeans.modules.profiler.ui.profilepoints.ProfilePointUI$Location.getUrl(ProfilePointUI.java:297)
        at 
org.netbeans.modules.profiler.ui.profilepoints.ProfilePointUI$Location.toMethodSourceCodeSelection(ProfilePointUI.java:351)
        at 
org.netbeans.modules.profiler.ui.profilepoints.ProfilePointUI$Location.toSourceCodeSelection(ProfilePointUI.java:338)
        at 
org.netbeans.modules.profiler.ui.profilepoints.ProfilePointsManager.overrideRootMethods(ProfilePointsManager.java:147)
        at 
org.netbeans.modules.profiler.ui.profilepoints.ProfilePointsManager.startNewSession(ProfilePointsManager.java:135)
        at 
org.netbeans.modules.profiler.NetBeansProfiler.connectToStartedApp(NetBeansProfiler.java:520)
        at 
org.netbeans.modules.profiler.ant.NBProfileDirectTask$1.run(NBProfileDirectTask.java:297)
        at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
[catch] at 
java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
        at 
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
        at 
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
        at 
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
Comment 1 ehucka 2006-05-26 14:07:50 UTC 
I have specified only start profiling and stop profiling points and the 
exception is throwing always I start profiling by profiling points.
Comment 2 Maros Sandor 2006-05-26 14:34:30 UTC 
Your stacktrace is out of date and I cannot reproduce it. Please attach updated
stacktrace and write some steps to reproduce.
Comment 3 ehucka 2006-05-26 16:52:51 UTC 
It's from daily build of trunk profiler 060526. I have not newer build. There
was start and stop profiling points in one method. Nothing more.
Comment 4 ehucka 2006-05-30 14:34:12 UTC 
updated stacktrace

java.lang.IllegalStateException: getUrl called from AWT thread
org.netbeans.modules.profiler.ui.profilepoints.ProfilePointUI$Location.getUrl(ProfilePointUI.java:301)
org.netbeans.modules.profiler.ui.profilepoints.ProfilePointUI$Location.toMethodSourceCodeSelection(ProfilePointUI.java:355)
org.netbeans.modules.profiler.ui.profilepoints.ProfilePointUI$Location.toSourceCodeSelection(ProfilePointUI.java:342)
org.netbeans.modules.profiler.ui.profilepoints.ProfilePointsManager.overrideRootMethods(ProfilePointsManager.java:147)
org.netbeans.modules.profiler.ui.profilepoints.ProfilePointsManager.startNewSession(ProfilePointsManager.java:135)
org.netbeans.modules.profiler.NetBeansProfiler.connectToStartedApp(NetBeansProfiler.java:520)
org.netbeans.modules.profiler.ant.NBProfileDirectTask$1.run(NBProfileDirectTask.java:297)
Comment 5 Maros Sandor 2006-05-30 16:35:52 UTC 
I see, there is something broken there if you specify a profiling point location
by a method name.
Comment 6 Maros Sandor 2006-06-01 10:20:12 UTC 
My check there is intentional to prevent MDR lookup in AWT. So, the first thing
I would like to know whether call to NetBeansProfiler.connectToStartedApp is
intended to be made from AWT. I guess that starting profiler engine in event
dispatching thread is not a good idea. Tomas? Jirka?
Comment 7 ehucka 2006-06-01 10:33:20 UTC 
those are my words :-)
Comment 8 Tomas Hurka 2006-06-01 13:11:07 UTC 
Yes, this is not a good idea.
Comment 9 Jiri Sedlacek 2006-12-07 13:25:49 UTC 
Fixed as a side effect of rewrite to Retouche.
Comment 10 ehucka 2007-01-11 17:30:35 UTC 
verified