Error during Upgrade from 5.1 to 6.3

Cynthia Fehr
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 26, 2015

Hello,

I'm trying to upgrade from 5.1 to 6.3.

During the upgrade I get this error:

gmai 10.101.10.101 /secure/admin/XmlRestore.jspa [atlassian.jira.upgrade.UpgradeManagerImpl] Upgrade Task: 'Updating radiobutton and multi-checkbox searchers to be multi-select searchers' succeeded 2015-02-25 11:03:43,174 JiraImportTaskExecutionThread-1 INFO admin 653x143x1 9jgmai

10.101.10.101 /secure/admin/XmlRestore.jspa [atlassian.jira.upgrade.UpgradeManagerImpl] Setting current build number to 810 2015-02-25 11:03:43,180 JiraImportTaskExecutionThread-1 INFO admin 653x143x1 9jgmai

10.101.10.101 /secure/admin/XmlRestore.jspa [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Shorten name of index on ManagedConfigurationItem entity 2015-02-25 11:03:43,189 JiraImportTaskExecutionThread-1 ERROR admin 653x143x1 9j

gmai 10.101.10.101 /secure/admin/XmlRestore.jspa [atlassian.jira.upgrade.UpgradeManagerImpl] Exception thrown during upgrade: Already closed. java.sql.SQLException: Already closed.         at org.apache.commons.dbcp.PoolableConnection.close(PoolableConnection.java:114)         at org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.close(PoolingDataSource.java:191)lready closedAlready closed

        at org.ofbiz.core.entity.jdbc.interceptors.connection.DelegatingConnection.close(DelegatingConnection.java:76)

 

1 answer

1 accepted

0 votes
Answer accepted
Cynthia Fehr
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 6, 2015

The answer to this one was that another application sharing the same database as JIRA, with high input and output requirements, seemed to be blocking the upgrade.  We shut it down and the problem disappeared.

Suggest an answer

Log in or Sign up to answer