[#JRA-9198] JVM crash with Sun JDK 1.5.0_06

JIRA

JVM crash with Sun JDK 1.5.0_06

Created: 31/Jan/06 12:04 AM Updated: 09/Oct/06 12:16 PM

Component/s:

Import / Export

Affects Version/s:

3.5.1

Fix Version/s:

3.5.2

Time Tracking:

Not Specified

Environment:

jdk 1.5_06_b05

Issue Links:

Duplicate

This issue duplicates:

~~JRA-10131~~ segmentation fault in the Java virtual machine

Participants:	Adrian Hempel, Anton Wenzelhuemer, David Zuttermeister, Donna McGahan [Atlassian], Dylan Etkin [Atlassian], Jeff Turner [Atlassian], Mark Chaimungkalanont [Atlassian], Nick Menere [Atlassian], Ted Dunning and Tom Moore
Since last comment:	2 years, 38 weeks, 3 days ago
Resolution Date:	01/Mar/06 09:13 PM
Labels:

Description

« Hide

Some people have reported the JVM crashes during a BUgzilla import.

from the stack trace the relevent lines are:

Current thread (0x080f2b38):  JavaThread "CompilerThread0" daemon [_thread_in_native, id=8380]

and

Current CompileTask:
opto:1605 org.apache.lucene.index.IndexReader$1.doBody()Ljava/lang/Object; (99 bytes)

I believe they are seeing the same JVM bug as reported at:
http://forum.java.sun.com/thread.jspa?threadID=691320&tstart=1

It refers to the bug:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6355639

It looks like it affects only the latest jvm 1.5_06-b05 (well the people all seem to be using it).
Workarounds include:

You could perhaps try downgrading jvm's.

Excluding that class from compilation:

-XX:CompileCommand=exclude,org/apache/lucene/index/IndexReader\$1,doBody

We have also ahd some reports of this affecting 1.5.0_05 as well

All

Comments

Work Log

Change History

Sort Order:

[ Permalink | « Hide ]

Nick Menere [Atlassian] added a comment - 31/Jan/06 04:49 PM

Another workaround is to increase your maximum heap size. E.g. from 256 to 512

[ Permalink | « Hide ]

Mark Chaimungkalanont [Atlassian] added a comment - 12/Feb/06 07:20 PM

Other suggestions to workaround this problem include setting the perm size to a higher value, so you could also add

-XX:MaxPermSize=256m

[ Permalink | « Hide ]

Mark Chaimungkalanont [Atlassian] added a comment - 19/Feb/06 04:56 PM

more related threads:

http://www.nabble.com/Re:-JVM-Crash-in-Lucene-t1081217.html

[ Permalink | « Hide ]

Dylan Etkin [Atlassian] added a comment - 01/Mar/06 09:13 PM

I have added the flag to the standalone which should come out when 1.5.0_07 comes out and have added a message that shows in the logs when the app is started if we detect the version of the jvm from sun.

[ Permalink | « Hide ]

Adrian Hempel added a comment - 20/Mar/06 10:56 PM

The fix breaks JIRA on Mac OS X 10.3 Server with the following JRE:

java version "1.4.2_09"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_09-233)
Java HotSpot(TM) Client VM (build 1.4.2-56, mixed mode)

Workaround is to remove the -XX:CompileCommand option from setenv.sh

[ Permalink | « Hide ]

Nick Menere [Atlassian] added a comment - 22/Mar/06 12:14 AM

Adrian,
Thanks for the heads up. this issue is being tracked at - ~~JRA-9635~~.

[ Permalink | « Hide ]

Jeff Turner [Atlassian] added a comment - 12/May/06 05:01 AM

Yes it does also affect 1.5.0_05-b05

[ Permalink | « Hide ]

Tom Moore added a comment - 18/May/06 12:38 PM

Can someone explain to me where to put these fixes? Where do I add that "compile" option... where would I add the maxheap size, etc

[ Permalink | « Hide ]

David Zuttermeister added a comment - 18/May/06 02:28 PM

Hey Tom -

If you're running Jira as a Windows Service, you'll want to see this doc:
http://www.atlassian.com/software/jira/docs/latest/runasservice.html

If not, you can edit your setenv.sh on linux and OS X, setenv.bat on windows.

cheers,
dz

[ Permalink | « Hide ]

Jeff Turner [Atlassian] added a comment - 29/May/06 09:15 PM

Sun have recently released 1.5.0_07 which should fix this problem.

[ Permalink | « Hide ]

Ted Dunning added a comment - 22/Sep/06 05:04 PM

We just replicated a very similar problem using 1.5.0_08 so it doesn't look like 07 fixed the problem.

Our problem occured while updating a moderate sized Lucene index rather than using Jira, but it looks like the problem is the same.

[ Permalink | « Hide ]

Nick Menere [Atlassian] added a comment - 25/Sep/06 07:43 PM

Ted,

Are you able to attach the resultant error file - hs_err_pid****.log
This should contain the exact error we are facing.

cheers,
Nick

[ Permalink | « Hide ]

Anton Wenzelhuemer added a comment - 09/Oct/06 04:53 AM

Hi,

why is this issue set to resolved/fixed? what is the fix?

We are experiencing the same error and we do not do any bugzilla or other import.

jira 3.6.2 enterprise build 156; standalone version(tomcat 5.5.9); mysql 4.1.20, sun java 1.5.0_06, Linux 2.6.9-34.

what can I do?

regards, anton

[ Permalink | « Hide ]

Donna McGahan [Atlassian] added a comment - 09/Oct/06 12:16 PM

Anton,

Our recommended fix is to upgrade from JDK 1.5.0_06 to the latest JDK.

Cheers,
Donna