Bug ID: JDK-4415774 Linux: Java 1.3 does not run on Redhat 7.1

Type: Bug
Component: hotspot
Sub-Component: runtime
Affected Version: 1.3.0,1.3.0_02,1.3.1,1.4.0

Priority: P2
Status: Closed
Resolution: Fixed
OS: linux,linux_2.4
CPU: x86

Submitted: 2001-02-15
Updated: 2012-10-08
Resolved: 2001-03-23

Other	Other
1.3.1 rc1Fixed	1.4.0Fixed

The hotspot VM goes into a busy loop when run on the Redhat 7.1 beta release.
ie java -version

There have been many changes to glibc resulting in version 2.2.1 including a
variable thread stack size

This was reported by the mozilla and redhat teams

Name: krC82822			Date: 02/18/2001


jdk1.3.1 beta does not run with Glibc 2.2-3 with Redhat 7.1 fisher beta.


(Review ID: 117206)
======================================================================

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: ladybird-rc1 FIXED IN: ladybird-rc1 INTEGRATED IN: ladybird-rc1 merlin-beta

14-06-2004

EVALUATION Current JVM breaks on RedHat 7.1 with floating stack enabled because JVM assumes thread stacks have fixed 2M size and are aligned at 2M boundaries which are no longer true on Wolverine. With floating stack, we need to know exactly where the stack is in order to detect stack overflows. This is solved with a new function added into glibc (2.2.2-7). This bug will be fixed in JDK 1.3.1 RC1. hui.huang@Eng 2001-03-16 ------------ glibc 2.2.2-7 contains a bug. one has to wait for the next glibc build to use this fix. not sure what it would be called though. hui.huang@Eng 2001-03-22 ------------- The fix is already in JDK 1.3.1 RC1. But to get it work on floating stack, user would need glibc 2.2.3. As of today, glibc 2.2.3 is still in pre- release mode. One can get the source code from ftp://sourceware.cygnus.com/pub/glibc/releases/ Before it becomes widely available in RPM package, users who don't want to manually build from source code might just replace "libpthread-0.9.so" with the one that came with Redhat 7.0. hui.huang@Eng 2001-04-16 ---------------------------- The original problem is fixed in RC1, the new problem (java hang) with Redhat 7.1 FCS is due to a new feature introduced in RH 7.1 FCS. Please see 4447270 for details and possible workarounds. hui.huang@Eng 2001-04-19

19-04-2001

WORK AROUND ulimit -s 2000 calvin.austin@Eng 2001-02-16 Also change /usr/bin/cut to cut as per duplicate bug report calvin.austin@Eng 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 hui.huang@Eng 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". hui.huang@Eng 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. hui.huang@Eng 2001-04-19

16-04-2001

Duplicate :	JDK-4414722 - v1.3 won't work on Redhat 7.1 BETA (Fisher): GLIBC version 2.2.1-3.i686 problem?
Duplicate :	JDK-4420076 - Sun java 1.3.1beta build 15 dies with segmentation fault
Duplicate :	JDK-4472655 - hotspot crashes in JDK 1.3.0_02 and JDK1.3.0_04 on standard RedHat 7.1 config
Duplicate :	JDK-4450810 - java -version gave assertion on Redhat 7 machine.
Relates :	JDK-4480981 - LINUX: need a different way to detect floating stack pthread lib
Relates :	JDK-4445172 - Linux: Fatal: JVM can not locate libpthread.so!
Relates :	JDK-4447270 - Linux: Java 1.3.1 RC1 hang on Redhat 7.1 FCS