Oups previous email was out too quick
> IMNSHO, that kernel flag workaround is a joke. I almost fell out of my
> chair with laughter when I first read that proposed "solution" on the
> Sun forums. "Hey, our JDK makes some faulty assumptions about memory
> allocation and threading ... the solution is to direct Java to use the
> antiquated threading libraries indefinitely." LOL ... excellent
> "solution." Better still, it is STILL not fixed AFAIK (I d/led the
> latest release a few weeks ago). Even better than that, the hokey flag
> trick did not even WORK when I tried it the first week that all went
> down (dunno if it does now).
>
> The IBM JDK originally had the same problem, but was fixed literally
> within one week of Redhat 7.1 release. From what I've heard, it works on
> all distros without problem. Mad props to IBM for the extrememly quick
> fix, and for supporting its developers the right way. IBM rocks for Java
> support. (Jikes is an absolute Godsend.)
Redhat is not Linux and these problems is not related to Linux but to GNU
GLIBC.
SuSe, Mandrake and others recents distro use the new GLIBC 2.2 scheme and
people providing software for these distro should take care of it.
And JVM are very OS sensitive.
>I believe that, instead of blaming Sun for not putting out a workaround to
>that bug, probably the one to blame is RedHat for putting out such a buggy
>OS. I had to work around some issues with that OS myself writing the
Service
>code, and definitely, I wouldn't trust that "thing" not even to drive my
>coffee pot, but, of course, that's me. Get a decent and "real" OS, don't
>fight with those issues (Solaris 8 on x86 is far better, IMVHO, and it's
>downloadable for free... Soooo...)
Do you suggest us that Sun made a mistake releasing a JVM for a brain
damaged OS like Linux ?)
