JIRA Throw 'GenericValue cannot be null' Error after accessing the Browse Project page

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

  1. When accessing the Browse Project page, in the JIRA logs, trace like below can be found:

    2012-03-22 15:55:44,635 http-8080-28 ERROR      [500ErrorPage.jsp] Exception caught in 500 page GenericValue cannot be null.
    java.lang.IllegalArgumentException: GenericValue cannot be null.
        at com.atlassian.jira.ofbiz.AbstractOfBizValueWrapper.<init>(AbstractOfBizValueWrapper.java:25)
        at com.atlassian.jira.issue.link.IssueLinkType.<init>(IssueLinkType.java:32)
        at com.atlassian.jira.issue.link.DefaultIssueLinkTypeManager.buildIssueLinkType(DefaultIssueLinkTypeManager.java:205)
        at com.atlassian.jira.issue.link.DefaultIssueLinkTypeManager.getIssueLinkType(DefaultIssueLinkTypeManager.java:77)
        at com.atlassian.jira.issue.link.DefaultIssueLinkTypeManager.getIssueLinkType(DefaultIssueLinkTypeManager.java:66)
        at com.atlassian.jira.issue.link.IssueLink.getIssueLinkType(IssueLink.java:81)
        at com.atlassian.jira.issue.index.indexers.impl.SubTaskIndexer.addIndex(SubTaskIndexer.java:54)
        at com.atlassian.jira.issue.index.IssueDocument.getDocument(IssueDocument.java:40)
    
  2. Re-indexing JIRA does not helps fixing the issue and might throw another error like:

    java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException: GenericValue cannot be null.
    at com.atlassian.jira.index.FutureResult.await(FutureResult.java:35)
    at com.atlassian.jira.index.CompositeResultBuilder$CompositeResult.await(CompositeResultBuilder.java:82)
    at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexAll(DefaultIndexManager.java:243)
    

The following appears in the atlassian-jira.log:

2012-03-22 16:09:36,434 http-8080-19 WARN infpcor 969x31123x1 18knlws 172.16.197.187 /browse/TESTPROJECT [polscheit.jira.plugins.GanttProjectTabPanel] You have not configured an issue link type to be used as Gantt-Dependency!
2012-03-22 16:09:37,455 http-8080-19 ERROR      [500ErrorPage.jsp] Exception caught in 500 page GenericValue cannot be null.
java.lang.IllegalArgumentException: GenericValue cannot be null.
	at com.atlassian.jira.ofbiz.AbstractOfBizValueWrapper.<init>(AbstractOfBizValueWrapper.java:25)
	at com.atlassian.jira.issue.link.IssueLinkType.<init>(IssueLinkType.java:32)
    at com.atlassian.jira.issue.link.DefaultIssueLinkTypeManager.buildIssueLinkType(DefaultIssueLinkTypeManager.java:205)
    at com.atlassian.jira.issue.link.DefaultIssueLinkTypeManager.getIssueLinkType(DefaultIssueLinkTypeManager.java:77)
    at com.atlassian.jira.issue.link.DefaultIssueLinkTypeManager.getIssueLinkType(DefaultIssueLinkTypeManager.java:66)
    at com.atlassian.jira.issue.link.IssueLink.getIssueLinkType(IssueLink.java:81)
    at com.atlassian.jira.issue.index.indexers.impl.SubTaskIndexer.addIndex(SubTaskIndexer.java:54)
    at com.atlassian.jira.issue.index.IssueDocument.getDocument(IssueDocument.java:40)

Cause

Invalid issue link exist in the database

Resolution

Unable to render {include} The included page could not be found.

  1. Stop JIRA.
  2. Verify if there are any invalid links in the database with the below SQL:

    SELECT * FROM issuelink where LINKTYPE not in (select ID from issuelinktype);

    (info) If there any results returned, there are invalid links in the database. 

  3. Remove all invalid links with the following SQL:

    DELETE FROM issuelink where LINKTYPE not in (select ID from issuelinktype);

     

  4. Start JIRA.
  5. Reindex JIRA.
Last modified on Mar 30, 2016

Was this helpful?

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