|Summary:||SIGSEGV received with IBM JDK 1.4.1 /Red Hat Linux 3 (taroon)|
|Product:||Red Hat Enterprise Linux 3||Reporter:||deebas|
|Component:||IBMJava2-JRE||Assignee:||Patrick Macdonald <patrickm>|
|Status:||CLOSED WONTFIX||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2007-10-19 18:59:52 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description deebas 2005-06-17 18:53:35 UTC
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: Symptoms: 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: Always 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 2 Steve Russell 2005-07-18 16:08:20 UTC
Hi, 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 18:59:52 UTC
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: http://www.redhat.com/security/updates/errata/ 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.