Bug 160837 - SIGSEGV received with IBM JDK 1.4.1 /Red Hat Linux 3 (taroon)
SIGSEGV received with IBM JDK 1.4.1 /Red Hat Linux 3 (taroon)
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: IBMJava2-JRE (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Patrick Macdonald
Depends On:
  Show dependency treegraph
Reported: 2005-06-17 14:53 EDT by deebas
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-19 14:59:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
java core (377.94 KB, text/plain)
2005-06-17 14:57 EDT, deebas
no flags Details

  None (edit)
Description deebas 2005-06-17 14:53:35 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)

Description of problem:
Using an application that creates a lot of threads and
starts lots of processes.sometime JVMsthat are running the processes dies.Basically one controller program tries to ping the remoteobject but there is no reply back .
The java core shows a SIGSEGV received in ?? at in /websphere_5/appserver/java/jre/bin/libjitc.so.
Java cores created every couple of hours

java core attached

Version-Release number of selected component (if applicable):
OS Level         : 2.4.21-27.ELsmp.#1 SMP Wed Dec 1 21:59:02 EST 2004

How reproducible:

Steps to Reproduce:
Has anybody experienced similar problems ? Not sure if this is a bug or
an issue with a missing patch ..

Additional info:
Comment 1 deebas 2005-06-17 14:57:00 EDT
Created attachment 115632 [details]
java core
Comment 2 Steve Russell 2005-07-18 12:08:20 EDT

We saw this extensively.  Basically the in order to work on RHEL3 u need IBM 
1.4.2 sr1a or later (current is sr2).  Particularly bad when u use JNI, but 
that isn't the only thing that trips it.
Comment 3 RHEL Product and Program Management 2007-10-19 14:59:52 EDT
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.

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