Java 6 update 21, developer starting problem

Classic Servoy
1

yes there is a new update… I tested the client and that kept on running fine.
But the developer has suddenly a problem:

It is described here:

http://wiki.eclipse.org/FAQ_How_do_I_in … Eclipse%3F

“Eclipse 3.6 and below on Windows has a bug with Oracle/Sun JDK 1.6.0_21 (July 2010) where the launcher cannot detect a Oracle/Sun VM, and therefore does not use the correct PermGen size. If you are using either of this version, add the -XX flag to the eclipse.ini as described above.”

I guess oracles now did change the identifier of the JRE/JDK vm to “oracle” instead of sun. So now Eclipse doesnt see it is a Sun VM anymore and wont set the Perm size setting we have in the servoy.ini file like this:

–launcher.XXMaxPermSize
256m

What you can do to fix it is add another argument to the -vmargs so below the max mem settings we have:
-Xmx512m (512 can be some other number if you changed it or do have another default)
add a new line:
-XX:MaxPermSize=256M

and that 256M should be in sync with the size of --launcher.XXMaxPermSize.

2

:shock:

Why do they have to change the identifier of the VM? As if every Java user was looking at the VM identifier. And people how does, already know it’s not Sun any more but Oracle. :x

3

i dont know of course if that is true, it is just my guess, didnt look at the code how eclipse decides this is a sun vm.
But i guess they look at some identifier or name so that they know it is suns…

4

Oracle already reverted the change again in the next build of 6_u21 (build 07)

http://bugs.sun.com/bugdatabase/view_bu … id=6969236

problem is that that one is of course not released, so it will affect many eclipse users that upgrade now to u21…