500 errors after upgrade to 7.5

[Phillip Villarreal]

After completing the upgrade from 7.3 to 7.5 we are able to login and see the dashboard and admin pages.  All of the project and issue boards though respond with a 500 error message.  The following is a copy of the error details:

Version:1.0 StartHTML:000000208 EndHTML:000091460 StartFragment:000001216 EndFragment:000091366 StartSelection:000001216 EndSelection:000091347 SourceURL:http://jira.vlitech.local:8080/browse/MOBILIS Oops - an error has occurred

Referer URL: http://jira.vlitech.local:8080/secure/BrowseProjects.jspa?selectedCategory=all&selectedProjectType=all

java.lang.RuntimeException: com.atlassian.cache.CacheException: com.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.IllegalStateException: Invalid BundleContext.

[Stephen Greene]

The root of the problem here is the JDBC Driver for SQL Server changed for 7.5 Following these instructions found on the main website will fix it:

New JDBC driver for Microsoft SQL Server

We've shipped a new driver for Microsoft SQL Server, which requires that you update the driver's URL in the dbconfig.xml file. In most cases, it's enough to run the JIRA configuration tool, which will update the URL automatically, but if you've customized the URL by adding some properties to it, you might need to make the changes manually. 

  Show me how to do this...

Running the JIRA configuration tool

If you never customized the JDBC URL, run the JIRA config tool to update it.
1. Go to <installation-directory>/bin, and run the config.bat / config.sh file.
2. Click Save. Your configuration will be updated.
3. Restart JIRA.

After I followed these steps it began working again.

https://developer.atlassian.com/jiradev/latest-updates/preparing-for-jira-7-5

[Phillip Villarreal]

Our Jira deployment is basically out of commission until we get this fixed.  Does anyone know if they have a paid phone support where we can call someone to further assist?

[Gregory Van Den Ham]

Unfortunately, if you have a 10 user license, community is the option.  There are partners and contractors out there.

If you have everything backed up, you may be able to conduct a rollback. 

[Gregory Van Den Ham]

Anything else in the log files?   Did you document and resolve any file changes that the installer warned as changed during the upgrade?

Have you checked things like JVM (java memory) to see if that reset below your instance thresholds or run a full index?

[Phillip Villarreal]

Nothing that looks like an error in any log except the following, it is showing up in the atlassian-jira-gc log:

2017-09-26T08:46:17.645-0500: 70872.628: [GC (Allocation Failure) [PSYoungGen: 242362K->3988K(249344K)] 721764K->485359K(773632K), 0.0305269 secs] [Times: user=0.05 sys=0.00, real=0.03 secs]
2017-09-26T08:53:16.854-0500: 71291.836: [GC (Allocation Failure) [PSYoungGen: 243092K->1456K(250880K)] 724463K->484766K(775168K), 0.0248455 secs] [Times: user=0.05 sys=0.00, real=0.03 secs]
2017-09-26T08:53:17.229-0500: 71292.213: [GC (Allocation Failure) [PSYoungGen: 243120K->160K(251392K)] 726430K->484239K(775680K), 0.0185116 secs] [Times: user=0.03 sys=0.00, real=0.02 secs]
2017-09-26T08:53:17.604-0500: 71292.582: [GC (Allocation Failure) [PSYoungGen: 241824K->1627K(252416K)] 725903K->485818K(776704K), 0.0180873 secs] [Times: user=0.02 sys=0.00, real=0.02 secs]

No warnings issued by the installer.

JVM looks ok on RAM.  Running with default of 256M min and 768M max.

Successfully ran a full reindex.

[Phillip Villarreal]

One of my devastating found this error also:

Referer URL: http://jira.vlitech.local:8080/login.jsp?permissionViolation=true&os_destination=%2Fbrowse%2FMOBILIS-129&page_caps=&user_role=
com.google.template.soy.tofu.SoyTofuException: In 'print' tag, expression "$sidebarContent" evaluates to undefined.

[John Patounas]

For me as well after the upgrade to 7.5.0 I cannot edit any permission schemes any more as I get a status code 500 error