Jira server inaccessible with CacheException errors in logs

Related content

  • No related content found

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

The JIRA instance is not accessible and the following error can be found in the atlassian-jira.log log file:

2014-07-27 17:01:50,810 localhost-startStop-1 ERROR      [sal.core.lifecycle.DefaultLifecycleManager] Unable to start component: com.sun.proxy.$Proxy631
com.atlassian.util.concurrent.LazyReference$InitializationException: com.atlassian.cache.CacheException: java.lang.NullPointerException: com.atlassian.cache.memory.MemoryCacheManager$1$1@47ee0d3d returned null for key com.atlassian.cache.impl.ReferenceKey@0.
	at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:152)
	at com.atlassian.util.concurrent.LazyReference.get(LazyReference.java:115)
	at com.atlassian.greenhopper.Launcher.onSystemStartPhase(Launcher.java:190)
	at com.atlassian.greenhopper.Launcher.onStart(Launcher.java:169)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  <+2>
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
	at org.springframework.osgi.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:58)
	at org.springframework.osgi.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:62)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
	at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
	at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
	at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager.notifyLifecycleAwareOfStart(DefaultLifecycleManager.java:99)
Caused by: com.atlassian.cache.CacheException: java.lang.NullPointerException: com.atlassian.cache.memory.MemoryCacheManager$1$1@47ee0d3d returned null for key com.atlassian.cache.impl.ReferenceKey@0.
	at com.atlassian.cache.memory.DelegatingCachedReference.get(DelegatingCachedReference.java:47)
	at com.pyxis.greenhopper.jira.license.GreenHopperLicenseStoreImpl.retrieve(GreenHopperLicenseStoreImpl.java:35)
	at com.pyxis.greenhopper.jira.license.GreenHopperPluginLicenseManager.getCurrentLicense(GreenHopperPluginLicenseManager.java:102)
	at com.pyxis.greenhopper.jira.license.GreenHopperLicenseManagerImpl.doVerify(GreenHopperLicenseManagerImpl.java:131)
	at com.pyxis.greenhopper.jira.license.GreenHopperLicenseManagerImpl.verify(GreenHopperLicenseManagerImpl.java:121)
	at com.atlassian.greenhopper.Launcher$FullSystemInitialiser.<init>(Launcher.java:409)
	at com.atlassian.greenhopper.Launcher$1.create(Launcher.java:132)
	at com.atlassian.greenhopper.Launcher$1.create(Launcher.java:128)
	at com.atlassian.util.concurrent.LazyReference$Sync.run(LazyReference.java:326)
	at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:146)
	... 61 more
Caused by: java.lang.NullPointerException: com.atlassian.cache.memory.MemoryCacheManager$1$1@47ee0d3d returned null for key com.atlassian.cache.impl.ReferenceKey@0.
	at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:401)
	at com.atlassian.cache.memory.DelegatingCachedReference.get(DelegatingCachedReference.java:39)
	... 71 more

Cause:

This error may be caused by the JIRA Agile plugin and is tracked in the bug below:

Resolution:

There are the following alternatives to address this error:

Solution 1

  1. Stop your JIRA instance.
  2. In your JIRA server file system, browse to: JIRA_HOME/plugins/installed-plugins

  3. Search for the UPM (Universal Plugin Manager) plugins JAR file, and move the JAR file to a different folder.

    The name of the JAR file may be prepended with a number, such as: 
    846688264762062110.atlassian-universal-plugin-manager-plugin-2.7.6.jar

  4. Start your JIRA instance. (Now, the instance will start with the plugin uninstalled.)
  5. Wait a while to complete the startup, then try to access your JIRA instance.
  6. Move the .JAR file back to the installed-plugins folder

    In case you have multiple versions of the UPM in place, make sure you only move the newest one back

  7. Restart your JIRA instance


Solution 2

  1. Stop JIRA.
  2. Update the Universal Plugin Manager (Add-on Manager) by file replacement.
  3. Start JIRA.

Solution 3

  1. Stop your JIRA instance.
  2. In your JIRA server file system, browse to: JIRA_HOME/plugins/installed-plugins

  3. Search for the UPM (Universal Plugin Manager) plugin JAR file, and either move the file to a different folder or delete it.

    • The name of the JAR file may be prepended with a number, such as: 
      846688264762062110.atlassian-universal-plugin-manager-plugin-2.7.6.jar
    • In case you have multiple versions of the UPM in place, make sure you move or delete all them
  4. Start your JIRA instance. JIRA will start with its bundled UPM (Universal Plugin Manager) version.

Last modified on Feb 27, 2023

Was this helpful?

Yes
No
Provide feedback about this article

Related content

  • No related content found
Powered by Confluence and Scroll Viewport.