We've started to roll out RH7 on newly-deployed machines. Recently
we've discovered that the version of glibc shipped with RH7 (glibc-2.2)
has a bug which causes javac to return 0 values even if subprocesses
have encountered errors. A bug report in the JDK knowledge base lists
"upgrade to Red Hat 7.1" as the solution.
Well okay, so until 7.1 actually comes out, I thought I'd apply the
latest glibc (2.2.2). That fixed the problem with javac, but broke java
itself. From scratching my head over strace output, it seems as though
java now uses native threads instead of green threads, that doesn't
work, and java ends up stuck running nanosleep(2) forever, waiting for
one of its threads to check in.
So we've rolled back to glibc-2.2 and instructed all of our developers
to run javac with the -classic argument, which seems to avoid the
problems we're having but results in a significant performance hit.
[pausing to breathe]
Now my question: is anybody successfully using Java with native threads
on RH7? Any hints you could pass along?
--
Michael Jinks, IB // Technical Entity // Saecos Corporation
Opinions expressed above are my own, and not those of my employer.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
