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 62641 - Internal error: Expected InstrumentMethodGroupResponse
Summary: Internal error: Expected InstrumentMethodGroupResponse
Status: RESOLVED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Tomas Hurka
URL:
Keywords:
: 81499 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-08-19 08:51 UTC by vnicolici
Modified: 2007-01-08 17:01 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
messages.log (21.41 KB, text/plain)
2005-08-19 08:55 UTC, vnicolici 		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 vnicolici 2005-08-19 08:51:25 UTC 
I was doing memory liveness profiling, track every 10 allocations and record 
stack trace, and after about 18 hours, I got an error popup from the IDE:

Internal error:
Expected InstrumentMethodGroupResponse, got response of class class 
com.sun.tools.profiler.wireprotocol.Response,
value = NO TYPEOk, yes
All instrumentation will be removed

After this error, I got AIOOB exceptions when attempting to display life 
results, but I'm not sure that the errors are related.

Using XP SP2, JDK 1.5.0_04, NetBeans 4.1, NB profiler m8v2, profiling a J2EE 
web appplication running on Caucho Resin 3.0.14 Open Source app server.
Comment 1 vnicolici 2005-08-19 08:55:11 UTC 
Created attachment 24070 [details]
messages.log
Comment 2 J Bachorik 2006-08-08 13:14:21 UTC 
Seems to be related to race condition in communication protocol fixed in #69951
Comment 3 J Bachorik 2006-08-09 10:30:10 UTC 
A duplicate issue #81499 appeared after the aforementioned fix. So the fix don't
work on this issue.
Comment 4 J Bachorik 2006-08-09 10:31:44 UTC 
*** Issue 81499 has been marked as a duplicate of this issue. ***
Comment 5 Tomas Hurka 2007-01-08 17:01:34 UTC 
Hopefully fixed in trunk.