"Pier P. Fumagalli" wrote:
>
> Christopher Cain at [EMAIL PROTECTED] wrote:
> >
> > 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.)
>
> 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...)
As Henri points out, the problem lies in Java + Gnu C Stuff, not Java +
Redhat. Although Redhat certainly deserves its fair share of criticism
on buggy distro releases, primarily anything that ends in ".0", in this
case Redhat is not the culprit. I've heard widely divergant opinions on
who is to blame, Gnu or Sun, and the truth probably lies somewhere in
the middle. I sincerely doubt either product is completely blameless.
In any case, my only real criticism of Sun is that it is STILL not
fixed, and that they forgot to put the "work" in workaround (initially,
at least). By and large I am a big defender of Sun, and I certainly did
my fair share of Java advocacy during the early days of Blackdown, when
I couldn't swing a dead cat without hitting some GPL zealot who wanted
to whine about Java not being "Free As In Speech" and how everyone in
the Linux community should ignore it. I just think that Sun kind of hung
us Linux Java developers out to dry on this one. In contrast, IBM has
always been there for me as a developer; and no, I have no affiliation
to IBM whatsoever, I'm just a very satisfied customer.
But, since the the subject line does say DOC, I'll shut up now :-) ... I
justed wanted to clarify that it wasn't a *proper* Sun bashing I was
engaged in. If not for Sun, it's probably make my living slugging
through C++ ... or worse, God forbid, VB! ;-)
- Christopher
