Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 476695

Summary:	Sun JVM 1.5.0_17 crash with JBossAS 4.3.0-2.GA_CP01
Product:	Red Hat Enterprise Linux 5	Reporter:	Chris Duryee <cduryee>
Component:	java-1.5.0-sun	Assignee:	Deepak Bhole <dbhole>
Status:	CLOSED WONTFIX	QA Contact:	BaseOS QE <qe-baseos-auto>
Severity:	medium	Docs Contact:
Priority:	low
Version:	5.2	CC:	jamesnichols3
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-11 19:14:21 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Chris Duryee 2008-12-16 15:59:17 UTC

Description of problem:

When we run JBossAS 4.3.0-2.GA_CP01 with the Sun 1.5.0_17 JVM, we will see the following crash within five minutes:

#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  SIGSEGV (0xb) at pc=0x00002af0b777f6c4, pid=4198, tid=1091778880
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0_17-b04 mixed mode)
# Problematic frame:
# V  [libjvm.so+0x5bc6c4]
#

When we use the Sun 1.5.0_16 JVM, this doesn't happen.

We thought this might be a prelinking issue, but we ran the prelinker by hand and the problem still occurs. This is on an x86_64 Xen guest, with a x86_64 host. We were able to reproduce this on multiple Xen guests.

We saw this issue with two different sets of webapps deployed, on different hosts.

Version-Release number of selected component (if applicable): Sun JVM 1.5.0_17


How reproducible: every time


Steps to Reproduce:
1. deploy some webapps to the container
2. start jboss

  
Actual results: JVM crash


Expected results: no crash


Additional info: We have some machines that we can easily upgrade to _17, if you want a test scenario. Just let me know.

Comment 1 Lillian Angel 2008-12-16 21:24:27 UTC

test scenario would be great. thanks

Comment 2 JimNichols 2009-03-08 21:56:23 UTC

I am seeing this issue as well.  It happens almost instantly after startup and sometimes goes at least an hour or two before occurring.

What do I need to do to submit my test case?

Comment 3 Lillian Angel 2009-03-09 12:39:43 UTC

please attach it to this bug report.

Comment 4 JimNichols 2009-03-09 13:28:24 UTC

What exactly do you need for the test case?

Comment 5 Deepak Bhole 2010-06-28 22:00:59 UTC

We need the easiest possible way to reproduce this issue with minimal code.

Comment 6 Deepak Bhole 2013-03-11 19:14:21 UTC

java-1.5.0-sun is no longer shipped in RHEL-5.