Tempo Holiday Scheme Screen Crashes

Ranganathan May 5, 2016

Hi, 

We recently uppgraded to JIRA 6.4.12 and initially the Tempo Holiday Scheme screen was working. 

Recently when we tried to access the screen, it is getting crashed, same with the Workload scheme screen.

When we check the Logs, we found the following error:

2016-05-05 15:55:25,376 ajp-bio-172.00.000.000-8009-exec-804 ERROR XXXXX 955x2263974x1 j82l88 172.00.00.000 /secure/TempoHolidayScheme!default.jspa [velocity] Exception rendering #parse(com/tempoplugin/core/admin/help.vm) at com.tempoplugin.tempo-core:tempo-holiday-scheme-ww//com/tempoplugin/core/holiday/holidayScheme.vm[line 14, column 13]
2016-05-05 15:55:25,376 ajp-bio-172.00.000.000-8009-exec-804 ERROR XXXX 955x2263974x1 j82l88 172.00.00.000 /secure/TempoHolidayScheme!default.jspa [com.atlassian.velocity.DefaultVelocityManager] MethodInvocationException occurred getting message body from Velocity: java.lang.NoClassDefFoundError: Could not initialize class com.tempoplugin.core.buildinfo.BuildInfo
java.lang.NoClassDefFoundError: Could not initialize class com.tempoplugin.core.buildinfo.BuildInfo
at com.tempoplugin.core.admin.TempoAdminFunction$TempoHelper.getHelpTextPrefix(TempoAdminFunction.java:86)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.apache.velocity.runtime.parser.node.PropertyExecutor.execute(PropertyExecutor.java:142)

 

Could not found any resolution when googled. 

 

 

1 answer

0 votes
Steven F Behnke
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.
May 6, 2016

What does "getting crashed" mean? Perhaps there's an error on-screen, an HTTP 500 error, or it freezes up?

Have you tried disabling and reenabling the add-on? Perhaps reinstalling the add-on? Maybe stopping and starting your JIRA?

Suggest an answer

Log in or Sign up to answer