JIRA cannot be accessed after upgrading to JIRA 7
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Problem
After upgrading to JIRA 7, user is unable to access any page.
The following appears in the atlassian-jira.log
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
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 :
1
2
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'.ℹ️DF_AO_60DB71DESCR_3572E547 is a constraint on table: dbo.AO_60DB71_SWIMLANE
Then we see this error :
1
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 tableWhich 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.
Solution
Workaround
Drop the constrain on the affected table as per http://stackoverflow.com/questions/9866989/alter-table-on-dependant-column
1
ALTER TABLE AO_60DB71_QUICKFILTER DROP CONSTRAINT [DF__AO_60DB71__DESCR__30AE302A]Was this helpful?