yjp.exe doesn't start with Java 6 (jdk 1.6.0-ea) installed
-
- Posts: 64
- Joined: Mon Jan 10, 2005 7:13 pm
yjp.exe doesn't start with Java 6 (jdk 1.6.0-ea) installed
This applies to version 3.2 and 4.0 build 504.
Starting yjp.exe yields a "YourKit Java Profiler 4.0 EAP cannot run with Java version 1.6.0-ea, it requires Java 1.4.2 or 5.0." startup message.
Running "javaw -jar yjp.jar" works fine.
Starting yjp.exe yields a "YourKit Java Profiler 4.0 EAP cannot run with Java version 1.6.0-ea, it requires Java 1.4.2 or 5.0." startup message.
Running "javaw -jar yjp.jar" works fine.
-
- Posts: 64
- Joined: Wed Oct 06, 2004 7:56 am
As far as I know YourKit doesn't yet support Java 6. I've also tried both 3.2 and the 4.0 EAP on Java 6 for interests sake but I wasn't suprised when I found it didn't work as I didn't expect it to (thus why I didn't post it as a bug report).
Can I just ask what you are using Java 6 for? Is it meerly out of curiosity (like I was) or are you planning to use it on some kind of project for which you would require profiling?
Can I just ask what you are using Java 6 for? Is it meerly out of curiosity (like I was) or are you planning to use it on some kind of project for which you would require profiling?
-
- Posts: 64
- Joined: Mon Jan 10, 2005 7:13 pm
I installed it just out of curiosity. Sometimes it's fun to live on the bleeding edge.
In my post I forgot to mention that I am not usually using Java 6. I usually run 1.5 (or 1.4), and that's what I want yjp to run with.
If I had to guess I'd say yjp.exe searches the JavaSoft registry part for the highest available JDK entry, which is 1.6 on my system. Unless, of course, I have got things terribly wrong.
I'd probably uninstall Java 6, b/c a smooth yjp ride is more important for me.
In my post I forgot to mention that I am not usually using Java 6. I usually run 1.5 (or 1.4), and that's what I want yjp to run with.
If I had to guess I'd say yjp.exe searches the JavaSoft registry part for the highest available JDK entry, which is 1.6 on my system. Unless, of course, I have got things terribly wrong.
Code: Select all
C:\>set JAVA_HOME
JAVA_HOME="C:\Program Files\Java\jdk1.5.0"
Code: Select all
C:\>C:\WINDOWS\system32\java -version
java version "1.5.0_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_01-b08)
Java HotSpot(TM) Client VM (build 1.5.0_01-b08, mixed mode, sharing)
-
- Posts: 64
- Joined: Mon Jan 10, 2005 7:13 pm
FWIW, I was probably right. Just deleted the keys
from the registry, and yjp.exe starts just fine.
Would it be possible to fix yjp.exe?
Code: Select all
HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Development Kit\1.6
HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Development Kit\1.6.0
Would it be possible to fix yjp.exe?
-
- Posts: 1626
- Joined: Tue Aug 10, 2004 7:52 pm
-
- Posts: 64
- Joined: Wed Oct 06, 2004 7:56 am
-
- Posts: 1626
- Joined: Tue Aug 10, 2004 7:52 pm
Bugfix buid #506 is available at http://www.yourkit.com/eap/
Enjoy!
Enjoy!
-
- Posts: 64
- Joined: Mon Jan 10, 2005 7:13 pm
Wow, that fix was fast!
Just to let you know: yjp now starts with yjp.exe, the installed Java 6 is used, though.
As for Java 6: I've used it very little, and there seems to have changed little up to now. Here's an interesting read about it. http://weblogs.java.net/blog/peterkessl ... the_f.html
Just to let you know: yjp now starts with yjp.exe, the installed Java 6 is used, though.
As for Java 6: I've used it very little, and there seems to have changed little up to now. Here's an interesting read about it. http://weblogs.java.net/blog/peterkessl ... the_f.html
-
- Posts: 1626
- Joined: Tue Aug 10, 2004 7:52 pm
-
- Posts: 64
- Joined: Wed Oct 06, 2004 7:56 am
-
- Posts: 64
- Joined: Wed Oct 06, 2004 7:56 am
Thanks rblasch, that was an interesting article and explains somewhat why so little significant progress appears to have been made so far (not a complaint at all, just an early observation). I would still think that many of these bugs being fixed in Mustang should also be fixed in the 1.5 minor releases through. The main issue against the takeup of 1.5 for me is the lack of Mac support for it, though I'm hopeful this will be resolved.rblasch wrote:As for Java 6: I've used it very little, and there seems to have changed little up to now. Here's an interesting read about it.