I am creating a new image(i.e distribution) for a diskless lab at the University I work for. I was using redhat 7.0 for the base but decided to redo it using redhat 7.1. I really need sun's jdk on there, and thought there would be no problem, since it worked on 7.0. I installed it last night version jdk1.3_02 using the rpm from Sun. When I tried to run "java" it complained about not finding "/usr/bin/cut". I knew that was not a big deal...a symlink fixed it ('cut" is in /bin). After that was fixed I still had problems; when I ran java it complained that it couldn''t find "libjvm.so". At this point I was through with the rpm, so I downloaded the self extracting file(which can be downloaded on the same page from sun). It installed correctly and got rid of the other previous problems. However when I try to run a program it just hangs. After I killing the hanging program it prints out:

[root@pepperfly IDE]# /usr/java/jdk1.3.0_02/bin/java PicB
# # An unexpected exception has been detected in native code outside the VM.# Program counter=0x40043350
#
# Problematic Thread: prio=1 tid=0x804db68 nid=0x139f runnable

Also, after I kill the java program, 4 or 5 java processes keep running in the background. Xosview reports 100% cpu usage and a 5.8 load! Someone else in my department (working independtly) has come across the same problem.

Does anyone have any idea?

I don't have an answer for you, but I'll share my experience. I'm using Redhat 7.0, and I've downloaded the jdk1.3 as well. It works fine for console programs, but when I create a gui with AWT or SWING, none of the components appear, and on the console I get a font not found error, repeatedly. I don't understand how to fix this, or why it's a problem, but I think it has something to do with jdk1.3. This all happened about 2 months ago, so when I need to create a gui, or do something graphically, I go to another computer in my house.

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

My thanks goes out to woodchuck. I used your workaround -- I had redhat 7.0 on another disk in my computer. I just copied it over. This is my first time using this web site, or anything like. It saved my alot of hours.

Note: I tried to find bug information on the java homepage and the redhat homepage, but I could find it. I'll visit the java developer homepage from now on.