Jira crashing with error 500

Leena Bakshi

After upgrading jira to 7.3.3, I started adding plugins one by one and jira never crashed other than one Add on didnt let the navigation tree ( on the left side of the page) load properly and it said "unable to render elements due to an error" so I ran reindexing, that didnt help but reboot did. Yesterday I installed the final add on -"Jenkins integration with Jira" and I could still access Jira with no problem for hours until when I decided to test Service desk and there I saw the same error again on the left side of the page "Unable to render element due to an error" however I could see the issues/ticket listed on the right side in different Service desks. So I did the same reindexing that didnt solve the problem. I could still access jira though and I decided to reboot the machine and then I couldnt access jira and got error 500 with the following details:

Any idea??

 Cause

Referer URL: https://jiradev73.xxx.com/secure/errors.jsp

java.lang.NoClassDefFoundError: Could not initialize class webwork.dispatcher.GenericDispatcher

java.lang.NoClassDefFoundError: Could not initialize class webwork.dispatcher.GenericDispatcher        at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.prepareDispatcher(JiraWebworkActionDispatcher.java:205) [classes/:?]

somethingblue

Hi Leena,

When you upgraded JIRA, what version did you upgrade from? 

I commonly see the "Unable to render element due to an error" in conjunction with an upgrade that was not performed per the JIRA Service Desk 3.2.x release notes.

We have a knowledge base article titled After upgrading to JIRA Service Desk 3.2.x or greater, Service Desk project's navigation bar shows "Unable to render element due to an error" that describes this error and how to resolve it.

Take a look in the atlassian-jira.log to see if you see errors similar to the following:

2016-08-30 22:12:51,923 http-nio-8320-exec-11 ERROR anonymous 1332x78x3 8rur7t 0:0:0:0:0:0:0:1 /browse/DESK [c.a.p.webresource.assembler.DefaultWebResourceAssembler] Error generating bigpipe content for 'sidebar-id': java.lang.NullPointerException
java.util.concurrent.CompletionException: java.lang.NullPointerException
 at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:273)
 at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:280)
 at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1592)
 at com.atlassian.jira.plugin.bigpipe.PrioritizedRunnable.run(PrioritizedRunnable.java:31)
 at com.atlassian.jira.plugin.bigpipe.BigPipeService.lambda$executeSingleTask$1(BigPipeService.java:59)
 at java.util.Optional.map(Optional.java:215)

[c.a.p.webresource.assembler.DefaultWebResourceAssembler] Error generating bigpipe content for 'sidebar-id': Deadline exceeded 
Error generating bigpipe content for 'activity-panel-pipe-id': Deadline exceeded 

In addition, check the atlassian-servicedesk.log for messages such as the following:

2016-08-30 22:10:07,438 UpmAsynchronousTaskManager:thread-1 ERROR anonymous 1332x78x3 8rur7t 0:0:0:0:0:0:0:1 /rest/plugins/1.0/available/featured [atlassian.servicedesk.bootstrap.lifecycle] '2.3.6' version of Service Desk cannot be upgraded to '3.2.0-038-01'. Upgrade to '3.0.0' <= <version> < '3.2.0' first. com.atlassian.servicedesk.bootstrap.upgrade.UnsatisfiedVersionRequirementException: '2.3.6' version of Service Desk cannot be upgraded to '3.2.0-038-01'. Upgrade to '3.0.0' <= <version> < '3.2.0' first. at com.atlassian.servicedesk.bootstrap.upgrade.UpgradeRequirementsChecker.checkVersionRequirementForUpgrade(UpgradeRequirementsChecker.java:25) at com.atlassian.servicedesk.bootstrap.lifecycle.PluginLifeCycle.checkAndRunUpgrades(PluginLifeCycle.java:256) at com.atlassian.servicedesk.bootstrap.lifecycle.PluginLifeCycle.runPluginStartupSideEffectsImpl(PluginLifeCycle.java:183) at com.atlassian.servicedesk.bootstrap.lifecycle.LifecycleLock.writeImpl(LifecycleLock.java:97) at com.atlassian.servicedesk.bootstrap.lifecycle.LifecycleLock.runOnStartup(LifecycleLock.java:75)

Take a look at After upgrading to JIRA Service Desk 3.2.x or greater, Service Desk project's navigation bar shows "Unable to render element due to an error" for the resolution based on the errors you see.

Cheers,

Branden