Hmm, from digging through the code this is very much impossible. The monitoring 
thread, that refreshes the live results (that cause the DumResultsResponse to 
be received) is nto started until after the connectToServer method finishes. 
Are you able to reproduce? Can you get threads dump of the profiled VM when 
this happens? Do you remember the stape that lead to this (i.e. previous 
profiling finishing in some non-standard way)?

I've seen this two times, but I'm not able to reproduce it. I've just played 
with webapp profiling, several times profiled CPU and watched live results, no 
problems when finishing previous profiling session. I'll try to provide more 
info if I see this again.

Closing for now, please reopen when you get this again.

Seen again: profiled memory alloc, stopped profiling and tried to start memory 
liveness:

*********** Exception occurred ************ at 2:58 PM on Jan 2, 2006
java.lang.ClassCastException: 
com.sun.tools.profiler.wireprotocol.VMPropertiesResponse
        at com.sun.tools.profiler.ProfilerClient.forceObtainedResultsDump
(ProfilerClient.java:530)
        at 
org.netbeans.modules.profiler.LiveResultsWindow.callForceObtainedResultsDump
(LiveResultsWindow.java:332)
        at org.netbeans.modules.profiler.LiveResultsWindow.access$600
(LiveResultsWindow.java:55)
        at org.netbeans.modules.profiler.LiveResultsWindow$5.run
(LiveResultsWindow.java:356)
        at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:471)
[catch] at org.openide.util.RequestProcessor$Processor.run
(RequestProcessor.java:904)
*********** Exception occurred ************ at 2:58 PM on Jan 2, 2006
java.lang.ClassCastException: 
com.sun.tools.profiler.wireprotocol.DumpResultsResponse
        at com.sun.tools.profiler.ProfilerClient.connectToServer
(ProfilerClient.java:1321)
        at com.sun.tools.profiler.ProfilerClient.establishConnectionWithServer
(ProfilerClient.java:134)
        at com.sun.tools.profiler.TargetAppRunner.connectToStartedVMAndStartTA
(TargetAppRunner.java:577)
        at com.sun.tools.profiler.TargetAppRunner.connectToStartedVMAndStartTA
(TargetAppRunner.java:171)
        at com.sun.tools.profiler.TargetAppRunner.connectToStartedVMAndStartTA
(TargetAppRunner.java:166)
        at org.netbeans.modules.profiler.NetBeansProfiler.connectToStartedApp
(NetBeansProfiler.java:532)
        at org.netbeans.modules.profiler.ant.NBProfileDirectTask$1.run
(NBProfileDirectTask.java:266)
        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)

I got this exception while the profiler was starting up (performance profiling,
one root method, java core classes filtered). The last profiled process was
still running (because of Issue #72013). Exception raised when I switched
between the zombie and current output tab.

*** Issue 73373 has been marked as a duplicate of this issue. ***

Increasing priority as it occurs more frequently.

*** Issue 76858 has been marked as a duplicate of this issue. ***

Fix in progress...

*** Issue 80190 has been marked as a duplicate of this issue. ***

Fixed in trunk.

Fix merged to release55 branch

*** Issue 80866 has been marked as a duplicate of this issue. ***

Haven't seen since the fix.