JDK 1.6.0_10 release candidate released

[Roedy Green]

JDK 1.6.0_10 release candidate released.

downloado at http://java.sun.com/javase/downloads/ea.jsp

 

[Andreas Leitgeb]

JDK 1.6.0_10 release candidate released.
downloado at http://java.sun.com/javase/downloads/ea.jsp

Has anyone else tried it, yet?

On my machine (Linux 32bit) processes running with this
version of Java cannot be attached to with jconsole.

I've two versions installed: 1.6.0_06 and the 1.6.0_10(rc),
It doesn't matter which version of jconsole I use, I can
only attach to processes running with ..._06 but not to
those running with ..._10. These processes run exactly
the same application class files (not even a .jar), so the
difference must be on Java's side.

The symptom of not-working is, that jconsole gives up after a
while, writing: "The connection to 23456 did not succeed. Would
you like to try again?"

Can anyone confirm this? Perhaps also on other platforms?

 

[Knute Johnson]

Has anyone else tried it, yet?

On my machine (Linux 32bit) processes running with this
version of Java cannot be attached to with jconsole.

I've two versions installed: 1.6.0_06 and the 1.6.0_10(rc),
It doesn't matter which version of jconsole I use, I can
only attach to processes running with ..._06 but not to
those running with ..._10. These processes run exactly
the same application class files (not even a .jar), so the
difference must be on Java's side.

The symptom of not-working is, that jconsole gives up after a
while, writing: "The connection to 23456 did not succeed. Would
you like to try again?"

Can anyone confirm this? Perhaps also on other platforms?

Andreas:

It's working fine for me.

 

[zerg]

The symptom of not-working is, that jconsole gives up after a
while, writing: "The connection to 23456 did not succeed. Would
you like to try again?"

If you're using a software firewall, it will need to be told to let the
1.6.0_10 JVM talk to network ports, but has presumably long since been
told to let the 1.6.0_06 JVM do so.

If that's not the problem, then it may be an actual bug in 1.6.0_10.

 

[Andreas Leitgeb]

Andreas:
It's working fine for me.

from your posting-headers, I assume you're on windows. Right?
(just for the record of where it does work and where it does not)

 

[Andreas Leitgeb]

If you're using a software firewall, it will need to be told to let the
1.6.0_10 JVM talk to network ports, but has presumably long since been
told to let the 1.6.0_06 JVM do so.

I'm on linux, and I'm not aware of any software that would decide
net-permissions program-specifically. I'm 100% sure, not to have
configured anything else for jdk1.6.0_06 back when I installed it.

If that's not the problem, then it may be an actual bug in 1.6.0_10.

Ok, I'll search the bug-database now. Perhaps someone already reported
it meanwhile (then I could still vote for it)

 

[dominicreynolds]

I'm on linux, and I'm not aware of any software that would decide
net-permissions program-specifically.  I'm 100% sure, not to have
configured anything else for jdk1.6.0_06 back when I installed it.


Ok, I'll search the bug-database now.  Perhaps someone already reported
it meanwhile (then I could still vote for it)

Is jconsole part of the JDK? Could be be that the jconsole version is
specific to a JDK version? So that you would need a specific version
of jconsole for _10.

 

[Knute Johnson]

from your posting-headers, I assume you're on windows. Right?
(just for the record of where it does work and where it does not)

Yes Windows XP SP3. I have both JDK 1.6.0_10 and JRE 1.6.0_10-rc
installed. The JRE overwrites the one from the JDK install.

 

[Knute Johnson]

from your posting-headers, I assume you're on windows. Right?
(just for the record of where it does work and where it does not)

And I assume your having trouble on Linux?

I tried it on my Fedora 9 with the OpenJDK. It won't connect to any of
my programs but it will connect to the jconsole. I found a couple of
web articles that mention problems with the hostname. If hostname -i
shows 127.0.0.1 it won't work. I tried getting mine to point to the
DHCP address I'm using and I still couldn't get it to work.

So there you go. I'm clueless.

 

[Nigel Wade]

Has anyone else tried it, yet?

On my machine (Linux 32bit) processes running with this
version of Java cannot be attached to with jconsole.

I've two versions installed: 1.6.0_06 and the 1.6.0_10(rc),
It doesn't matter which version of jconsole I use, I can
only attach to processes running with ..._06 but not to
those running with ..._10. These processes run exactly
the same application class files (not even a .jar), so the
difference must be on Java's side.

The symptom of not-working is, that jconsole gives up after a
while, writing: "The connection to 23456 did not succeed. Would
you like to try again?"

Can anyone confirm this? Perhaps also on other platforms?

I've just tried it here, and it works fine. I can connect to a 1.6.0_10-rc JVM
using either the same version jconsole or the jconsole from 1.6.0_07-b06. This
is on RHEL5, 32bit.

Are you connecting jconsole to the Java process by PID? This is the only
mechanism I've tested.

 

[Andreas Leitgeb]

Is jconsole part of the JDK?

Yes, it is. (It's in the "bin"-subfolder of "${java.home}")

Could be be that the jconsole version is
specific to a JDK version?

jconsole (1.6.0_10) was able to inspect a process running
in an older 1.6.0_06 vm, but not the other one running in
a vm of same version (as jconsole).

Since no one else mentioned reproducability, I'll just watch
it further and wait for the next rc-version.

 

[Andreas Leitgeb]

And I assume your having trouble on Linux?

No need to assume. I wrote it explicitly

I tried it on my Fedora 9 with the OpenJDK. It won't connect to any of
my programs but it will connect to the jconsole.

What version (of Java) is that? Or is it a non-sun product?
Anyway, here, the 1.6.0_10 jconsole doesn't even connect to itself.

I found a couple of web articles that mention problems with the
hostname. If hostname -i shows 127.0.0.1 it won't work.

Interesting... If that's the problem, it wasn't one for 1.6.0_06.

Btw., my hostname -i points to "127.0.1.1" (two ones), so I'm not
sure if 127.0.0.1 related troubles affect me :-/
I will do some more tests for that.

So there you go. I'm clueless.

Thanks, anyway.

 

[Knute Johnson]

Yes, it is. (It's in the "bin"-subfolder of "${java.home}")


jconsole (1.6.0_10) was able to inspect a process running
in an older 1.6.0_06 vm, but not the other one running in
a vm of same version (as jconsole).

Since no one else mentioned reproducability, I'll just watch
it further and wait for the next rc-version.

1.6.0_10-rc has a new tool, Jvisualvm. Similar but with a profiler too.

 

[Andreas Leitgeb]

I've just tried it here, and it works fine. I can connect to a 1.6.0_10-rc JVM
using either the same version jconsole or the jconsole from 1.6.0_07-b06. This
is on RHEL5, 32bit.

Are you connecting jconsole to the Java process by PID? This is the only
mechanism I've tested.

Actually, I connected by clicking the process in jconsole's dialog,
but I got similar results for some other utilities, like jmap <pid>.

 

[Roger Lindsjö]

Has anyone else tried it, yet?

On my machine (Linux 32bit) processes running with this
version of Java cannot be attached to with jconsole.

Can anyone confirm this? Perhaps also on other platforms?

I tried with 1.6.0_07 and 1.6.0_10, and I can connect jconsole to a
running process for any permutation of the two versions.

This is on 2.6.23.17-88.fc7.

 

[Andreas Leitgeb]

I tried with 1.6.0_07 and 1.6.0_10, and I can connect jconsole to a
running process for any permutation of the two versions.
This is on 2.6.23.17-88.fc7.

My current theory is, that it depends less on the version, but
on how busy the application to be watched is.

When I first reported it here, the process running on _10
was already quite large in memory, and causing the machine
to heavy swapping. When I Ctrl-Z'ed it, and started another
process with a different version of Java, that one was fast
enough to respond, so it was attach-able. As it seems, those
java-utilities(*) are just ways too impatient

*: jconsole, jmap, jvisualvm, ...