Symptoms

JIRA will stop without warning and without information logged in the normal places. The following can be found in the 

The following appears in the atlassian-jira.log:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00000000026da253, pid=4548, tid=5384
#
# JRE version: 7.0-b147
# Java VM: Java HotSpot(TM) 64-Bit Server VM (21.0-b17 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# J  org.apache.lucene.index.DocInverterPerField.processFields([Lorg/apache/lucene/document/Fieldable;I)V
#
# Core dump written. Default location: C:\Program Files\Atlassian\JIRA\bin\hs_err_pid4548.mdmp
#
# An error report file with more information is saved as:
# C:\Program Files\Atlassian\JIRA\bin\hs_err_pid4548.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
#

Diagnosis

Typically, this is only seen when running a Java 7 version earlier than 1.7_u21. Please check the version number of your Java components, found at Administration -> System Info

Cause

The cause of this issue is a low level incompatibility between Java 1.7 earlier than update 21 and certain versions of Windows.

Resolution

• Install an appropriate Java version to your system

• Set your JAVA_HOME variable to point at its location

  Based on your operational needs, it is suitable to declare your JAVA_HOME in the setenv.sh file. In this case, the variable will only affect JIRA.