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.
Hi, I am having trouble profiling with the new Mustang JDK 6. The first issue would be that the linked library mentioned in the docs does not exist for jdk 6 - that is, the directory /profiler1/modules/profiler-ea-libs/deployed/jdk15 exists, but there is no corresponding jdk1.6 directory. No problem, I entered the line as "/jdk1.6/bin/java -agentpath:/opt/netbeans/profiler1/modules/profiler-ea-libs/deployed/jdk15/linux/libprofilerinterface.so=/opt/netbeans/profiler1/modules/profiler-ea-libs,5140" as specified in the userdocs, and it appears to run to the point where my app is waiting for the ide to connect. The problem is that the ide wants to "calibrate". It gives instructions for this, which I follow. I recieve a "calibration performed, data saved successfully" message from the ide, and the following in my app vm console: JFluid: waiting for connection on port 5140 JFluid: local connection with the tool Starting calibration... JFluid: connection with agent closed Agent_OnLoad called... Agent_OnLoad completed successfully. + exit at which point the app exits. I restart the app, and try to connect from the ide again.... at which point the ide says "Since you did not run the Profiler on this machine or target JVM before, deleted the saved calibration data, or this data is corrupt, profiling will STOP now. You have to run the calibration command for your target JVM before running the profiler again... To perform calibration, please invoke the "Profile| Advanced Commands | Run Profiler Calibration" command" I am at a loss as to how to run the profiler with the JDK/jvm 6 (mustang) on Linux. Is it supported? Thanks, Sean Erickson "
Hi Sean, Thank you for reporting this problem. Calibration has to be done separately for each JVM version supported by JFluid. The JVM set by default is the 1.4.2 customized VM bundled with the profiler. So to run calibration for Mustang (JDK 6), you first have to point the profiler at it through "Profile -> Global settings -> Target JVM", then invoke the calibration command. However, this doesn't look very intuitive, so we should find a better way to address this problem in the next milestone release. Misha Dmitriev, JFluid/NetBeans Profiler team
Now the user is always prompted to select java platform for calibration. Fixed post M7 RC1.
Verification of old issues.
Closing old issues.