症状

1. On 64bit JVMs on Linux, JIRA crashes with a SIGSEGV fault. The process is no longer running.

2. A stack overflow error may appear in the logs:

   2009-07-20 06:02:04,232 TP-Processor15 ERROR [jira.event.issue.IssueEventDispatcher] Exception thrown from listener [com.pyxis.green
   hopper.jira.customfields.GreenHopperCTFIndexer] : null
   java.lang.StackOverflowError
   at org.apache.log4j.helpers.PatternParser$DatePatternConverter.convert(PatternParser.java:433)
   at org.apache.log4j.helpers.PatternConverter.format(PatternConverter.java:56)
   at org.apache.log4j.PatternLayout.format(PatternLayout.java:495)
   at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:292)
   at org.apache.log4j.WriterAppender.append(WriterAppender.java:150)
   at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:221)
   at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:57)
   at org.apache.log4j.Category.callAppenders(Category.java:187)
   at org.apache.log4j.Category.forcedLog(Category.java:372)
   at org.apache.log4j.Category.log(Category.java:864)
   at org.ofbiz.core.util.Debug.log(Debug.java:135)
   at org.ofbiz.core.util.Debug.log(Debug.java:127)
   at org.ofbiz.core.util.Debug.logWarning(Debug.java:294)
   at org.ofbiz.core.entity.jdbc.SQLProcessor.rollback(SQLProcessor.java:141)
   at org.ofbiz.core.entity.jdbc.SQLProcessor.commit(SQLProcessor.java:114)
   at org.ofbiz.core.entity.jdbc.SQLProcessor.close(SQLProcessor.java:153)
   at org.ofbiz.core.entity.GenericDAO.select(GenericDAO.java:456)
   at org.ofbiz.core.entity.GenericHelperDAO.findByPrimaryKey(GenericHelperDAO.java:77)
   at org.ofbiz.core.entity.GenericDelegator.findByPrimaryKey(GenericDelegator.java:534)
   at org.ofbiz.core.entity.GenericDelegator.findByPrimaryKey(GenericDelegator.java:569)
   at com.atlassian.jira.issue.managers.DefaultIssueManager.getIssue(DefaultIssueManager.java:61)
   at com.atlassian.jira.issue.managers.DefaultIssueManager.getIssueObject(DefaultIssueManager.java:210)
   at sun.reflect.GeneratedMethodAccessor45.invoke(Unknown Source)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at com.atlassian.util.profiling.object.ObjectProfiler.profiledInvoke(ObjectProfiler.java:71)
   at com.atlassian.jira.config.component.SwitchingInvocationHandler.invoke(SwitchingInvocationHandler.java:28)
   at $Proxy3.getIssueObject(Unknown Source)
   at com.atlassian.jira.issue.link.IssueLink.getIssueObject(IssueLink.java:133)
   at com.atlassian.jira.issue.link.IssueLink.getDestinationObject(IssueLink.java:100)
   at com.atlassian.jira.config.DefaultSubTaskManager.getSubTaskObjects(DefaultSubTaskManager.java:400)
   at com.atlassian.jira.issue.IssueImpl.getSubTaskObjects(IssueImpl.java:925)
   at com.pyxis.greenhopper.jira.customfields.RankingCFType.getBaseIssueForSubtaskRanking(RankingCFType.java:652)
   

原因

Please see GHS-1465 and GHS-1467 for further information.

ソリューション

There is a patch for this issue at GHS-1357. The problem is corrected permanently in version 4.0 of the JIRA Agile add-on.