This is an identified (and fixed) defect with JDK and glibc 2.2.2. The JDC web site lists several workarounds. In true 'path of least resistance' fashion, I used the symlink to cut and ulimit workarounds, and java at least runs (hello world works
). Your actual mileage may vary...
You can go read all about it on the JDC site (developer.java.sun.com) if you're so inclined. Bug numbers 4415774, 4414722, 4420076, 4445172, 4447270.
Here're the workarounds from the sun website:
ulimit -s 2000
xxxxx@xxxxx 2001-02-16
Also change /usr/bin/cut to cut as per duplicate bug report
xxxxx@xxxxx 2001-02-20
Floating stack is only enabled when glibc is compiled for linux-i686
(--enable-kernels=2.4.0). One can get around the problem by installing
glibc-2.2.*-i386.rpm which does not have floating stack.
Another possible workaround:
download glibc and glibc-linuxthreads source code
./configure --enable-add-ons
make
copy <glibc dir>/linuxthreads/libpthread.so to /lib/libpthread-0.9.so
xxxxx@xxxxx 2001-03-20
----------------
For those who don't want to build from source code and can't wait until
RH 7.1 FCS or glibc-2.2.3 being released, if you have access to a
Redhat 7.0 box, you can just copy over 'libpthread-0.9.so' from Redhat 7.0
to 7.1. libpthread in RH 7.0 uses fixed stack by default.
libpthread-0.9.so is normally placed under "/lib".
xxxxx@xxxxx 2001-04-16
------------------------------
With Redhat 7.1 FCS, "setenv LD_ASSUME_KERNEL 2.2.5", this will cause
JVM to link with glibc compiled for 2.2 kernel.
xxxxx@xxxxx 2001-04-19