JIRA cannot be accessed after upgrading to JIRA 7

Still need help?

The Atlassian Community is here for you.

Ask the community

This article only applies to Atlassian's server products. Learn more about the differences between cloud and server.

Problem

After upgrading to JIRA 7, user is unable to access any page. 

The following appears in the atlassian-jira.log

016-05-23 14:18:11,966 http-nio-8080-exec-15 ERROR ross 858x2728x1 1isj01k 172.16.101.36 /secure/Dashboard.jspa [o.a.c.c.C.[.[.[.[jsp.decorators.general_002dhead_002dpre_jsp]] Servlet.service() for servlet jsp.decorators.general_002dhead_002dpre_jsp threw exception
com.atlassian.cache.CacheException: com.atlassian.activeobjects.internal.ActiveObjectsInitException: bundle [com.pyxis.greenhopper.jira]
	at com.atlassian.cache.memory.DelegatingCachedReference.get(DelegatingCachedReference.java:62)
...
Caused by: com.atlassian.activeobjects.internal.ActiveObjectsInitException: bundle [com.pyxis.greenhopper.jira]
	at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects$1$1$1.call(TenantAwareActiveObjects.java:95)
	at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects$1$1$1.call(TenantAwareActiveObjects.java:86)
	at com.atlassian.sal.core.executor.ThreadLocalDelegateCallable.call(ThreadLocalDelegateCallable.java:42)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	... 1 more
Caused by: com.atlassian.activeobjects.internal.ActiveObjectsSqlException: There was a SQL exception thrown by the Active Objects library:
Database:
	- name:Microsoft SQL Server
	- version:10.00.5538
	- minor version:0
	- major version:10
	- name:jTDS Type 4 JDBC Driver for MS SQL Server and Sybase
	- version:1.3.1

java.sql.SQLException: The object 'DF__AO_60DB71__DESCR__375B2DB9' is dependent on column 'DESCRIPTION'.
...
Caused by: java.sql.SQLException: The object 'DF__AO_60DB71__DESCR__375B2DB9' is dependent on column 'DESCRIPTION'
...
 

Diagnosis

Environment

  • JIRA 7

Diagnostic Steps

We can see the in the logs the following :

2016-05-23 21:06:45,016 active-objects-init-JiraTenantImpl{id='system'}-0 ERROR ross     [n.java.ao.sql] Exception executing SQL update <ALTER TABLE dbo.AO_60DB71_SWIMLANE ALTER COLUMN DESCRIPTION NVARCHAR(255)>
java.sql.SQLException: The object 'DF__AO_60DB71__DESCR__3572E547' is dependent on column 'DESCRIPTION'.

(info)DF_AO_60DB71DESCR_3572E547 is a constraint on table: dbo.AO_60DB71_SWIMLANE

Then we see this error :

2016-05-23 21:06:45,016 active-objects-init-JiraTenantImpl{id='system'}-0 WARN ross     [n.j.ao.db.SQLServerDatabaseProvider] Error in schema creation: The object 'DF__AO_60DB71__DESCR__3572E547' is dependent on column 'DESCRIPTION'.; attempting to roll back last partially generated table

Which shows that the table was only partially generated and then rolled back. This would mean that JIRA software is only partially installed and there are issues in the database which is what's causing the issue.

Cause

The upgrade didn't run on the database correctly and it's rolling back the table creation.

Workaround

Drop the constrain on the affected table as per http://stackoverflow.com/questions/9866989/alter-table-on-dependant-column

ALTER TABLE AO_60DB71_QUICKFILTER DROP CONSTRAINT [DF__AO_60DB71__DESCR__30AE302A]
Last modified on May 24, 2016

Was this helpful?

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