- This topic has 7 replies, 3 voices, and was last updated 15 years, 6 months ago by Brian Fernandes.
-
AuthorPosts
-
frankc01aMemberI am getting the following exception:
java.lang.UnsupportedOperationException at com.sun.tools.visualvm.jvm.JVMImpl.getSystemProperties(JVMImpl.java:290) at com.sun.tools.visualvm.jvmstat.application.JvmstatApplication.createStorage(JvmstatApplication.java:71) at com.sun.tools.visualvm.core.datasource.DataSource.getStorage(DataSource.java:137) at com.sun.tools.visualvm.heapdump.impl.HeapDumpProvider.processNewApplication(HeapDumpProvider.java:163) at com.sun.tools.visualvm.heapdump.impl.HeapDumpProvider.access$500(HeapDumpProvider.java:61) at com.sun.tools.visualvm.heapdump.impl.HeapDumpProvider$ApplicationListener$1.run(HeapDumpProvider.java:202) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:572) [catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:997)
And here is my configuration:
*** Date: Saturday, June 20, 2009 8:02:59 AM EDT ** System properties: OS=MacOSX OS version=10.5.7 Java version=1.5.0_19 *** MyEclipse details: MyEclipse Enterprise Workbench Version: 7.5 Build id: 7.5-20090609 *** Eclipse details: MyEclipse Enterprise Workbench Version: 7.5 Build id: 7.5-20090609 Eclipse Platform Version: 3.4.2.R342_v20090122-9I96EiWElHi8lheoJKJIvhM3JfVsYbRrgVIWL Build id: M20090211-1700 Eclipse Java Development Tools Version: 3.4.2.r342_v20081217-7o7tEAoEEDWEm5HTrKn-svO4BbDI Build id: M20090211-1700 Eclipse Plug-in Development Environment Version: 3.4.2.R342_v20090122-7T7U1E9imVKz-A8Vz-p_jRS Build id: M20080703-0800 Eclipse Graphical Editing Framework GEF Version: 3.4.2.v20090218-1145-67728084A56B4I233613552 Build id: 200809101400 Eclipse RCP Version: 3.4.200.R342_v20090122-989JESTEbig-SVaL8UJHcYBr4A63 Build id: M20090211-1700 Eclipse startup command=-os macosx -ws carbon -arch x86 -showsplash -launcher /Applications/Genuitec/MyEclipse 7.1/myeclipse.app/Contents/MacOS/myeclipse -name Myeclipse --launcher.library /Applications/Genuitec/MyEclipse 7.1/myeclipse.app/Contents/MacOS//../../../../Common/plugins/org.eclipse.equinox.launcher.carbon.macosx_1.0.101.R34x_v20080731/eclipse_1115.so -startup /Applications/Genuitec/MyEclipse 7.1/myeclipse.app/Contents/MacOS/../../../../Common/plugins/org.eclipse.equinox.launcher_1.0.101.R34x_v20081125.jar -clean -configuration ../../../configuration -keyring /Users/frankcastellucci/.eclipse_keyring -consoleLog -showlocation -vm /System/Library/Frameworks/JavaVM.framework
Brian FernandesModeratorFrank,
Thank you for the detailed report. I have a few questions:
1) Do you see this issue consistently or does it only occur sometimes?
2) Can you try keeping the VVM open and then invoke the profiling action from within MyEclipse again? Say yes to the warning dialog (about terminating existing profiling session) if it pops up, does this work?
3) What other Java applications are running on your machine, is it possible to reduce this to only MyEclipse? (and of course VVM and the app you are going to profile).
4) Go to Window > Preferences > MyEclipse > Profiler and let me know exactly what JDK version is selected on that page.
5) Please let me know what type of application you are attempting to profile (Java, Applet, Server) and what JRE is being used by the application (or the server).Thanks!
jannerMemberVisualVM is only working on Java 1.6 (you have 1.5.0_19 in your config).
Source: https://visualvm.dev.java.net/download.html (read under ‘possible problems’):
“VisualVM startup terminates by Error Starting VisualVM Dialog – unsupported version of Java: this typically happens when JRE or incorrect JDK version is used to run VisualVM, make sure VisualVM is running on Sun JDK 6+”Additionally make sure you have the latest Java update from Apple that contains the VisualVM:
http://support.apple.com/downloads/Java_for_Mac_OS_X_10_5_Update_4Jan
frankc01aMember@Support-Brian wrote:
Frank,
Thank you for the detailed report. I have a few questions:
1) Do you see this issue consistently or does it only occur sometimes?Each time
2) Can you try keeping the VVM open and then invoke the profiling action from within MyEclipse again? Say yes to the warning dialog (about terminating existing profiling session) if it pops up, does this work?
That worked.
3) What other Java applications are running on your machine, is it possible to reduce this to only MyEclipse? (and of course VVM and the app you are going to profile).
Didn’t matter whether 1 or 10 Java apps were running
4) Go to Window > Preferences > MyEclipse > Profiler and let me know exactly what JDK version is selected on that page.
JVM 1.6
5) Please let me know what type of application you are attempting to profile (Java, Applet, Server) and what JRE is being used by the application (or the server).
Java Server App in the MyEclipse Tomcat sandbox
Frank
frankc01aMember@janner wrote:
VisualVM is only working on Java 1.6 (you have 1.5.0_19 in your config).
Source: https://visualvm.dev.java.net/download.html (read under ‘possible problems’):
“VisualVM startup terminates by Error Starting VisualVM Dialog – unsupported version of Java: this typically happens when JRE or incorrect JDK version is used to run VisualVM, make sure VisualVM is running on Sun JDK 6+”Additionally make sure you have the latest Java update from Apple that contains the VisualVM:
http://support.apple.com/downloads/Java_for_Mac_OS_X_10_5_Update_4Jan
Jan,
I have the latest JVM from apple. Can you instruct me on how to change the MyEclipse startup configuration to use this?
Frank
Brian FernandesModeratorJan,
Thanks for the tip – installing the very latest JDK version would be a good idea and reduce the chances of VVM <> JVM incompatibility.
Just a few additional notes that may be helpful in general:
a) MyEclipse uses a separate JVM instance to run VisualVM (which you can configure/select on the MyEclipse > Profiler) preference page – the VM used to start Eclipse is not necessarily used. So even if you start Eclipse with 1.5, you could still run the profiler with 1.6.b) MyEclipse does not use the version of VVM that is part of the JDK selected, but instead uses a custom build of VVM which is part of MyEclipse. The JDK you select on the above page is just used to run this build.
frankc01aMemberOK,
So, there is no answer to the issue then?
I would still like to have MyEclipse running in the 1.6 JVM, but there is no apparent place to set that (separate issue).
Frank
Brian FernandesModeratorFrank,
For now I’m afraid not – you would need to let the VVM fail the first time and then leave it open for subsequent attempts – both VVM and your server appear to be running with the right JVM versions (you would probably see an error if these conditions were not met).
Just to confirm, even if you have just a single Java app running (MyEclipse) before you attempt profiling, you see the error you mentioned in your first post without fail?
As far as running MyEclipse with 1.6, that is currently not possible with Eclipse 3.4 due to an issue with the native OSX widgets, Java and SWT. In fact, MyEclipse has moved to Java 1.6 on Linux and Windows, but is forced to stick to 1.5 on the Mac due to this issue. 1.6 will be possible once we move to Eclipse 3.5.
Sorry for the inconvenience caused.
-
AuthorPosts