Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 32882 - Red Hat 7.1 RC2 java applications will not run
Red Hat 7.1 RC2 java applications will not run
Product: Red Hat Linux
Classification: Retired
Component: rpm (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
David Lawrence
: 32883 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2001-03-23 15:41 EST by Wendy Hung
Modified: 2008-08-01 12:22 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-03-23 15:54:18 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Wendy Hung 2001-03-23 15:41:32 EST
On Red Hat 7.1 RC2 java applications will not run. 

The JDK installed is IBM Java 1.1.8 installed from IBMJava118-SDK-1.1.8-5.0.i386.rpm. 
Whenever starting java, whether to compile using javac, or run using java, or to start up a jre the process appears to hang.
Looking at the process with "ps" we can see that its consuming around 98% cpu. 

I also tried two other versions of the JDK: IBM Java 1.3 and the linux port from Sun for Java 1.3. 

The IBM Java 1.3 behaved the same as the 1.1.8 version, while the Sun version allowed me to compile but attempting to 
run again resulted in a process that was hung consuming 98% of the cpu. 
The only way to kill the process is to issue a SIGKILL, SIGTERM has no effect. 
The java application I was attempting to run was a simple "Hello World" application.
Comment 1 Bill Nottingham 2001-03-23 15:53:28 EST
*** Bug 32883 has been marked as a duplicate of this bug. ***
Comment 2 Bill Nottingham 2001-03-23 15:54:14 EST
The JDK is buggy.

You can install the rawhide glibc, and run the JDK with the enivornment


set, and it should work.

Note You need to log in before you can comment on or make changes to this bug.