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 164344 - ClassCastException: org.netbeans.lib.profiler.wireprotocol.Response cannot be cast to org.netbeans.lib.profiler.wireprotocol.VMPropertiesResponse
Summary: ClassCastException: org.netbeans.lib.profiler.wireprotocol.Response cannot be...
Status: RESOLVED INVALID
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@profiler
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-03 19:56 UTC by Torbjorn Norbye
Modified: 2010-07-18 14:34 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 18975

Attachments
stacktrace (3.05 KB, text/plain)
2009-05-03 19:56 UTC, Torbjorn Norbye 		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 Torbjorn Norbye 2009-05-03 19:56:48 UTC 
Build: NetBeans IDE Dev (Build 090429)
VM: Java HotSpot(TM) 64-Bit Server VM, 11.3-b02-77, Java(TM) SE Runtime Environment, 1.6.0_13-b03-196
OS: Mac OS X, 10.5.6, x86_64

User Comments:
GUEST: Profiling a web application

strivedi: tried to use profiling by defining profile points then this error showed up.

tor: Tried to just "monitor" the application (not cpu or memory)



Stacktrace: 
org.openide.util.RequestProcessor$Item: task failed: java.lang.ClassCastException: org.netbeans.lib.profiler.wireprotocol.Response cannot be cast to org.netbeans.lib.profiler.wireprotocol.VMPropertiesResponse
        at org.openide.util.RequestProcessor$Item.fillInStackTrace(RequestProcessor.java:853)
        at java.lang.Throwable.<init>(Throwable.java:181)
        at java.lang.Exception.<init>(Exception.java:29)
        at org.openide.util.RequestProcessor$Item.<init>(RequestProcessor.java:819)
        at org.openide.util.RequestProcessor$Task.schedule(RequestProcessor.java:629)
        at org.openide.util.RequestProcessor.post(RequestProcessor.java:295)
Comment 1 Torbjorn Norbye 2009-05-03 19:56:53 UTC 
Created attachment 81436 [details]
stacktrace
Comment 2 Tomas Hurka 2009-05-04 08:21:08 UTC 
Please provide steps how to reproduce it - it works for me. Thanks.
Comment 3 matusdekanek 2009-09-18 12:11:37 UTC 
not reproduced since may - resolving invalid
Comment 4 mvfranz 2010-07-18 14:34:30 UTC 
I am not sure how easy this is to reproduce, but it does seem to happen enough that it is a real bug.

I was trying to profile a small application (1 class) that was doing file i/o and parsing XML.  I profiled everything.  It took a long time, instrumented 767 classes.  The connection was lost, and then I restarted, it never really connected.  I eventually had a port in use error, so I killed the process and then tried to restart profiling.  Somewhere during this process I noticed the red error symbol at the bottom right and submitted the bug.  This is in 6.9