JIRA 4.0 : Issue Caching Problems in early JIRA versions
This page last changed on Oct 31, 2007 by rosie@atlassian.com.
Early JIRA versions (confirmed JIRA 2.5.x and prior) suffer from occasional NPEs with stacktraces that look something like this:
com.ibm.ws.webcontainer.webapp.WebAppErrorReport: null<p><small><small><pre>java.lang.NullPointerException at java.util.LinkedList.remove(LinkedList.java(Compiled Code)) at org.ofbiz.core.util.UtilCache.get(UtilCache.java(Compiled Code)) at com.atlassian.jira.issue.cache.IssueCache.getIssue(IssueCache.java(Compiled Code)) at com.atlassian.jira.issue.cache.IssueCache.getIssue(IssueCache.java(Compiled Code)) at com.atlassian.jira.issue.cache.IssueCache.getIssue(IssueCache.java(Compiled Code)) ... This will occur somewhat randomly while Cache Issues, accessible in the General Configuration, is set to ON. The performance problem that lead to issue caching being necessary has been fixed in later versions, so the best option is to upgrade. Otherwise, you can disable issue caching at the cost of performance. |
![]() |
Document generated by Confluence on Oct 06, 2009 00:26 |