Details
-
Bug
-
Resolution: Fixed
-
Low
-
5.1.1, 5.1.5
-
5.01
-
Description
Symptom
When attempting to index JIRA, it fails with a RuntimeException that is caused by a NoSuchMethodError.
The following may be found within atlassian-jira.log:
java.lang.RuntimeException: java.util.concurrent.ExecutionException: com.atlassian.util.concurrent.LazyReference$InitializationException: com.atlassian.util.concurrent.LazyReference$InitializationException: com.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.NoSuchMethodError: com.atlassian.jira.issue.customfields.searchers.DateTimeRangeSearcher.<init>(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.jira.index.FutureResult.await(FutureResult.java:35) at com.atlassian.jira.index.CompositeResultBuilder$CompositeResult.await(CompositeResultBuilder.java:82) at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexAll(DefaultIndexManager.java:286) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.atlassian.util.profiling.object.ObjectProfiler.profiledInvoke(ObjectProfiler.java:81) at com.atlassian.jira.config.component.SwitchingInvocationHandler.invoke(SwitchingInvocationHandler.java:28) at $Proxy115.reIndexAll(Unknown Source) at com.atlassian.jira.util.index.CompositeIndexLifecycleManager.reIndexAll(CompositeIndexLifecycleManager.java:49) at com.atlassian.jira.web.action.admin.index.ReIndexAsyncIndexerCommand.doReindex(ReIndexAsyncIndexerCommand.java:27) at com.atlassian.jira.web.action.admin.index.AbstractAsyncIndexerCommand.call(AbstractAsyncIndexerCommand.java:54) at com.atlassian.jira.web.action.admin.index.AbstractAsyncIndexerCommand.call(AbstractAsyncIndexerCommand.java:23) at com.atlassian.jira.task.TaskManagerImpl$TaskCallableDecorator.call(TaskManagerImpl.java:359) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at com.atlassian.multitenant.impl.DefaultMultiTenantManager.runForTenant(DefaultMultiTenantManager.java:61) at com.atlassian.multitenant.juc.MultiTenantExecutors$WrappedRunnable.run(MultiTenantExecutors.java:160) at com.atlassian.jira.task.ForkedThreadExecutor$ForkedRunnableDecorator.run(ForkedThreadExecutor.java:249) at java.lang.Thread.run(Unknown Source) ... Caused by: java.lang.NoSuchMethodError: com.atlassian.jira.issue.customfields.searchers.DateTimeRangeSearcher.<init>(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.jira.ext.charting.searchers.FirstResponseDateSearcher.<init>(FirstResponseDateSearcher.java:24) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at org.picocontainer.defaults.InstantiatingComponentAdapter.newInstance(InstantiatingComponentAdapter.java:100) at org.picocontainer.defaults.ConstructorInjectionComponentAdapter.instantiateComponent(ConstructorInjectionComponentAdapter.java:200) at org.picocontainer.defaults.InstantiatingComponentAdapter.getComponentInstance(InstantiatingComponentAdapter.java:48) at org.picocontainer.defaults.DecoratingComponentAdapter.getComponentInstance(DecoratingComponentAdapter.java:42) at org.picocontainer.defaults.SynchronizedComponentAdapter.getComponentInstance(SynchronizedComponentAdapter.java:35) at org.picocontainer.defaults.DecoratingComponentAdapter.getComponentInstance(DecoratingComponentAdapter.java:42) at com.atlassian.jira.config.component.ProfilingComponentAdapter.getComponentInstance(ProfilingComponentAdapter.java:45) at org.picocontainer.defaults.DefaultPicoContainer.getComponentInstance(DefaultPicoContainer.java:298) at com.atlassian.jira.util.JiraUtils.loadComponent(JiraUtils.java:113) at com.atlassian.jira.util.JiraUtils.loadComponent(JiraUtils.java:91) at com.atlassian.jira.issue.managers.DefaultCustomFieldManager.getCustomFieldSearcher(DefaultCustomFieldManager.java:257) at com.atlassian.jira.issue.fields.CustomFieldImpl$CustomFieldSearcherLazyRef.create(CustomFieldImpl.java:1976) at com.atlassian.jira.issue.fields.CustomFieldImpl$CustomFieldSearcherLazyRef.create(CustomFieldImpl.java:1956) at com.atlassian.util.concurrent.ResettableLazyReference$InternalReference.create(ResettableLazyReference.java:143) at com.atlassian.util.concurrent.LazyReference$Sync.run(LazyReference.java:326) at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:146) ... 262 more
Cause
There is a problem with the UPM (see UPM-2450) where it is not recognising the latest version for the charting plugin - the current plugin version is incompatible with JIRA 5.1.1.
Resolution
Upgrade the plugin manually by downloading it from the Atlassian Marketplace and installing it with the Universal Plugin Manager.
Attachments
Issue Links
- mentioned in
-
Wiki Page Loading...