JIRA re-indexing fails due to incompatible database configuration

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

JIRA re-indexing will fail after reaching  around15 minutes or  around 80%. The following error is thrown in the UI:

Error stack trace:

org.ofbiz.core.util.GeneralRuntimeException: Error getting the next result (Closed Resultset: next)
        at org.ofbiz.core.entity.EntityListIterator.next(EntityListIterator.java:251)
        at com.atlassian.jira.ofbiz.DefaultOfBizListIterator.next(DefaultOfBizListIterator.java:136)
        at com.atlassian.jira.issue.util.DatabaseIssuesIterator.pullNextIssue(DatabaseIssuesIterator.java:92)
        at com.atlassian.jira.issue.util.DatabaseIssuesIterator.populateNextIssueIfNull(DatabaseIssuesIterator.java:56)
        at com.atlassian.jira.issue.util.DatabaseIssuesIterator.hasNext(DatabaseIssuesIterator.java:35)
        at com.atlassian.jira.util.collect.CollectionUtil.foreach(CollectionUtil.java:41)
        at com.atlassian.jira.issue.util.DatabaseIssuesIterable.foreach(DatabaseIssuesIterable.java:43)
        at com.atlassian.jira.issue.index.DefaultIssueIndexer.perform(DefaultIssueIndexer.java:242)

The following appears in the atlassian-jira.log:

2013-04-09 23:54:27,145 http-8080-9 WARN xxxx 1434x3720x4 1kpj7da 10.42.33.21,10.42.32.6 /s/en_UK-b3gfjb/734/4/aefcb9029706549036e514372c387539/_/download/contextbatch/js/atl.admin/batch.js [atlassian.plugin.webresource.DefaultResourceDependencyResolver] Cannot find web resource module for: com.atlassian.plugins.helptips.jira-help-tips:common
org.apache.commons.dbcp.AbandonedTrace$AbandonedObjectException: DBCP object created 2013-04-09 22:30:01 by the following code was never closed:
	at org.apache.commons.dbcp.AbandonedTrace.setStackTrace(AbandonedTrace.java:139)
	at org.apache.commons.dbcp.AbandonedObjectPool.borrowObject(AbandonedObjectPool.java:81)
	at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)

Cause

You are using JIRA 5.0 version and using some database configuration for JIRA 5.2 in the dbconfig.xml, such as:

    <pool-remove-abandoned>true</pool-remove-abandoned>    
    <pool-remove-abandoned-timeout>300</pool-remove-abandoned-timeout>

Resolution

Revert the changes in dbconfig.xml using the documentation of the exact version of JIRA - Connecting JIRA 5.0 to Database

 

The following appears in the atlassian-jira.log:

Last modified on Nov 2, 2018

Was this helpful?

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