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 105498 - Can't Profile Paint NBModule with JDK 5
Summary: Can't Profile Paint NBModule with JDK 5
Status: VERIFIED DUPLICATE of bug 105244
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: issues@profiler
URL:
Keywords: REGRESSION
Depends on:
Blocks:
 
Reported: 2007-06-03 13:36 UTC by Alexander Kouznetsov
Modified: 2007-07-05 14:15 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Profile output (2.52 KB, text/plain)
2007-06-03 13:40 UTC, Alexander Kouznetsov
Details
messages.log (93.68 KB, text/plain)
2007-06-03 13:40 UTC, Alexander Kouznetsov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kouznetsov 2007-06-03 13:36:37 UTC
NetBeans IDE Dev (Build 200705311200)
1.5.0_11; Java HotSpot(TM) Client VM 1.5.0_11-b03
Windows XP version 5.1 running on x86
ru_RU (nb); Cp1251

Steps to reproduce:
- Create Paint Sample Application
- Try to Profile it using default settings
- RESULT: Profiler fails with the following lines in the output: 

Profiler Agent: Waiting for connection on port 5140, timeout 10 seconds
(Protocol version: 6)
Profiler Agent: Established local connection with the tool
Profiler Agent: Connection with agent closed
Profiler Agent Error: Exception when handling command from client:
java.io.IOException: JFluid wire protocol error: code does not correspond to
command or response. Value -1

This issue is not reproducible with JDK 6 as well as with M9. This is also
reproducible with JDK 1.5.0_12-b04.
Comment 1 Alexander Kouznetsov 2007-06-03 13:37:02 UTC
Not reproducible with M9
Comment 2 Alexander Kouznetsov 2007-06-03 13:40:17 UTC
Created attachment 43157 [details]
Profile output
Comment 3 Alexander Kouznetsov 2007-06-03 13:40:47 UTC
Created attachment 43158 [details]
messages.log
Comment 4 Alexander Kouznetsov 2007-06-03 14:03:44 UTC
It seems that the module could be correctly profiled only once if no calibration
is needed. If calibration is performed automatically at the first profiler
invocation - it will break the ability to profile the application even for the
first run.
Comment 5 Tomas Hurka 2007-06-04 08:37:39 UTC

*** This issue has been marked as a duplicate of 105244 ***
Comment 6 Alexander Kouznetsov 2007-07-05 14:15:10 UTC
Verified the scenario with

Profiler 1.2 070703
Product Version: NetBeans IDE Dev (Build 200707031200) 
Java: 1.5.0_11; Java HotSpot(TM) Client VM 1.5.0_11-b03 
System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb)