Error "Description Time Level Exception" upon JIRA upgrade
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
Symptoms
Upon upgrading JIRA to JIRA version 6.x, the following error will be thrown :
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
JIRA Access Constraints
You cannot access JIRA at present.
Description Time Level Exception
An error occurred performing JIRA upgrade
The data before the upgrade has been exported to /var/atlassian/application-data/jira/export/jira_autoexport_20130612_052939.zip 2013-06-12 05:30:37 error
Exception thrown during upgrade: java.lang.NoSuchMethodError: com.atlassian.jira.issue.customfields.searchers.DateTimeRangeSearcher.(Lcom/atlassian/jira/security/JiraAuthenticationContext;Lcom/atlassian/jira/jql/operand/JqlOperandResolver;Lcom/atlassian/jira/util/velocity/VelocityRequestContextFactory;Lcom/atlassian/jira/config/properties/ApplicationProperties;Lcom/atlassian/velocity/VelocityManager;Lcom/atlassian/jira/web/action/util/CalendarLanguageUtil;Lcom/atlassian/jira/jql/util/JqlDateSupport;Lcom/atlassian/jira/issue/customfields/searchers/transformer/CustomFieldInputHelper;Lcom/atlassian/jira/timezone/TimeZoneManager;Lcom/atlassian/jira/datetime/DateTimeFormatterFactory;)V
com.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.NoSuchMethodError: com.atlassian.jira.issue.customfields.searchers.DateTimeRangeSearcher.(Lcom/atlassian/jira/security/JiraAuthenticationContext;Lcom/atlassian/jira/jql/operand/JqlOperandResolver;Lcom/atlassian/jira/util/velocity/VelocityRequestContextFactory;Lcom/atlassian/jira/config/properties/ApplicationProperties;Lcom/atlassian/velocity/VelocityManager;Lcom/atlassian/jira/web/action/util/CalendarLanguageUtil;Lcom/atlassian/jira/jql/util/JqlDateSupport;Lcom/atlassian/jira/issue/customfields/searchers/transformer/CustomFieldInputHelper;Lcom/atlassian/jira/timezone/TimeZoneManager;Lcom/atlassian/jira/datetime/DateTimeFormatterFactory;)V
at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:149)
at com.atlassian.util.concurrent.LazyReference.get(LazyReference.java:112)
at com.atlassian.util.concurrent.ResettableLazyReference.get(ResettableLazyReference.java:87)
...
Caused by: java.lang.NoSuchMethodError: com.atlassian.jira.issue.customfields.searchers.DateTimeRangeSearcher.(Lcom/atlassian/jira/security/JiraAuthenticationContext;Lcom/atlassian/jira/jql/operand/JqlOperandResolver;Lcom/atlassian/jira/util/velocity/VelocityRequestContextFactory;Lcom/atlassian/jira/config/properties/ApplicationProperties;Lcom/atlassian/velocity/VelocityManager;Lcom/atlassian/jira/web/action/util/CalendarLanguageUtil;Lcom/atlassian/jira/jql/util/JqlDateSupport;Lcom/atlassian/jira/issue/customfields/searchers/transformer/CustomFieldInputHelper;Lcom/atlassian/jira/timezone/TimeZoneManager;Lcom/atlassian/jira/datetime/DateTimeFormatterFactory;)V
...
at com.atlassian.util.concurrent.LazyReference$Sync.run(LazyReference.java:321)
at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:143)
... 38 more
Cause
The cause of the above error is the interference of Charting plugin after the upgrade is performed.
Workaround
The workaround for this error, is to disable Charting plugin.
If you are unable to access JIRA's UI:
In this case, you'll want to remove the plugin manually:
Shutdown JIRA
Navigate to: $JIRA_HOME/plugins/installed-plugins
Remove the charting plugins's *.jar file
It should have a filename similar to jira-charting-plugin-x.x.jar
Restart JIRA
Was this helpful?