Reindexing JIRA crashes the JRE

Still need help?

The Atlassian Community is here for you.

Ask the community


When reindexing JIRA the following error is found:

The following appears in the hs_err_pidxxxxxx.log file:

# A fatal error has been detected by the Java Runtime Environment:
#  SIGSEGV (0xb) at pc=0x00007fa3899f24d0, pid=11928, tid=140339511863040
# JRE version: 6.0_26-b03
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.1-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# J  org.apache.lucene.index.DocInverterPerField.processFields([Lorg/apache/lucene/document/Fieldable;I)V
# If you would like to submit a bug report, please visit:
VM Arguments:
jvm_args: -Djava.util.logging.config.file=/apps/atlassian/jira/conf/ -XX:MaxPermSize=256m -Xms1024m -Xmx1024m -Djava.awt.headless=true -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -XX:+PrintGCDateStamps -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Xmn512m -XX:SurvivorRatio=4 -XX:+PrintGCDetails -XX:+PrintGCApplicationConcurrentTime -XX:+PrintGCApplicationStoppedTime -XX:+PrintGCTimeStamps -XX:+PrintHeapAtGC -XX:+PrintTenuringDistribution -Xloggc:/apps/atlassian/jira/logs/gc.log -verbose:gc -XX:+UseParNewGC -XX:+OptimizeStringConcat -Djava.rmi.server.hostname=jirrt1.xint.xcorp.xsun -Djira.jelly.on=true -Dcom.atlassian.jira.plugin.ext.subversion.svnreadtimeout=2400000 -Dcom.atlassian.jira.plugin.ext.subversion.svnconnectiontimeout=2400000 -Datlassian.mail.senddisabled=true -Djava.endorsed.dirs=/apps/atlassian/jira/endorsed -Dcatalina.base=/apps/atlassian/jira -Dcatalina.home=/apps/atlassian/jira 
java_command: org.apache.catalina.startup.Bootstrap start
Launcher Type: SUN_STANDARD


This was caused by the following bug in Lucene and Java version 6u29 and the usage of the JVM parameter "OptimizeStringConcat". This parameter is not tested with use of JIRA and seems to have been experiencing problems in regards to this bug. We recommend removing it due to unpredictable behaviour.


  1. Shutdown JIRA
  2. Edit your (UNIX) or setenv.bat (Windows) file or your Windows service and remove the JVM argument "OptimizeStringConcat"
  3. Start JIRA again and reindex

Last modified on Mar 30, 2016

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.