Red Hat Bugzilla – Bug 37024
Sun Java JDK 1.3 interpreter does not work
Last modified: 2016-11-24 10:06:21 EST
From Bugzilla Helper: User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.2.19-7.0.1smp i686) JDK 1.3 was working good on Redhat 7.0, but in Redhat 7.1 First the compiler was not working until I made a copy the /bin/cut to the /usr/bin directory. Second.- Any class file ins not able to run with the java interpreter, seems like the process gets frozen. Reproducible: Always Steps to Reproduce: 1. Copy the /bin/cut file to /usr/bin directory 2. Compile any .java file with javac compiler from j2sdk 1.3 3. Run any .class with the java interpreter Actual Results: The compiler does not work until I copy the cut file The java interpreter does not run any program Expected Results: Compiler and interpreter working good like they do in Redhat 7.0
I am experiencing this problem with Red Hat Linux 7.1 and JDK 1.3.0_02 as well. In the process list the java interpreter is listed as [java <defunct>] and in a zombie state.
See RELEASE-NOTES: o Some Java JVMs (both from Sun and IBM) don't work with the new floating stack feature of the i686 version of glibc. The failures are due to programming assumptions in the JVMs that are now invalid. JVM vendors are working on making the necessary corrections. Until corrected JVM packages are available, you may force glibc to use the deprecated stack model by setting the following environment variable: LD_ASSUME_KERNEL=2.2.5 As for /bin/cut vs. /usr/bin/cut, you either have to make a symlink or adjust JDK scripts.
I have had good luck using the IBM JVM instead of the Sun JVM after coming across this bug in my 7.1 machine.