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 105023 - Remote profiling fails with StreamCorruptedException
Summary: Remote profiling fails with StreamCorruptedException
Status: VERIFIED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Tomas Hurka
URL:
Keywords: REGRESSION
Depends on:
Blocks:
 
Reported: 2007-05-29 13:58 UTC by Tomas Hurka
Modified: 2007-09-14 09:05 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
IDE log (45.96 KB, text/plain)
2007-05-29 13:59 UTC, Tomas Hurka 		Details
log from remote Java2D (2.43 KB, text/plain)
2007-05-29 14:02 UTC, Tomas Hurka 		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 Tomas Hurka 2007-05-29 13:58:03 UTC 
1) Start remote profiling of Java2D demo.
2) In NetBeans open Java2D sources and select CPU profiling / entire application / all classes
3) attach to remote JVM
4) open live results window

remote profiling fails with StreamCorruptedException or with 
java.io.IOException: JFluid wire protocol error: code does not correspond to command or response. 
Value ???

I will attach IDE log and log from remote Java2D application
Comment 1 Tomas Hurka 2007-05-29 13:59:50 UTC 
Created attachment 42890 [details]
IDE log
Comment 2 Tomas Hurka 2007-05-29 14:02:45 UTC 
Created attachment 42892 [details]
log from remote Java2D
Comment 3 Tomas Hurka 2007-05-30 10:05:55 UTC 
It looks like there is a race condition when sending profiling results over TCP/IP connection (only for 
remote profiling).
Comment 4 Tomas Hurka 2007-06-13 09:25:14 UTC 
Fixed in trunk.
Comment 5 Maksim Khramov 2007-09-14 09:05:19 UTC 
Verified in Beta1 build 200709111000