Update Atlassian Cache version to 2.8.3 for SD Data Center compatibility

XMLWordPrintable

    • 6.04

      Summary

      When installing Service Desk 2.5 with JIRA Data Center, initializing service desk will throw 500 error in the UI.

      Steps to reproduce

      1. Install Service Desk 2.5.2 on JIRA 6.4.10 Data Center
      2. Create/initialize Service Desk for the first time

      Actual result

      The following error is thrown in the logs:

      2015-08-25 19:32:55,635 http-bio-8080-exec-8 ERROR rkum66 1172x1363x1 1wiurfa 10.202.101.88,10.207.11.132 /secure/CreateIssueDetails.jspa [atlassian.event.internal.AsynchronousAbleEventDispatcher] There was an exception thrown trying to dispatch event [com.atlassian.jira.event.issue.IssueEvent@be75f57[issue=DI-7590,comment=<null>,worklog=<null>,changelog=<null>,eventTypeId=1,sendMail=true,params={eventsource=workflow, baseurl=https://dev3-atlassian.sapient.com/jira},subtasksUpdated=false]] from the invoker [SingleParameterMethodListenerInvoker{method=public void com.atlassian.servicedesk.bootstrap.listener.EventListenerLauncher.onIssueEvent(com.atlassian.jira.event.issue.IssueEvent), listener=com.atlassian.servicedesk.bootstrap.listener.EventListenerLauncher@44b86a51}]
      java.lang.RuntimeException: java.lang.NullPointerException
      	at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:54)
      	at com.atlassian.event.internal.AsynchronousAbleEventDispatcher$1$1.run(AsynchronousAbleEventDispatcher.java:48)
      	at com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:253)
      	at com.atlassian.event.internal.AsynchronousAbleEventDispatcher.dispatch(AsynchronousAbleEventDispatcher.java:107)
      	at com.atlassian.event.internal.EventPublisherImpl.invokeListeners(EventPublisherImpl.java:160)
      	at com.atlassian.event.internal.EventPublisherImpl.publish(EventPublisherImpl.java:79)
      	.......more
      Caused by: com.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.NullPointerException
      	at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:149)
      	at com.atlassian.util.concurrent.LazyReference.get(LazyReference.java:112)
      	at com.atlassian.servicedesk.internal.feature.queue.ProjectStateCacheManager.onIssueEvent(ProjectStateCacheManager.java:59)
      	at com.atlassian.servicedesk.bootstrap.listener.EventListenerLauncher.onIssueEvent(EventListenerLauncher.java:98)
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  <+1> (DelegatingMethodAccessorImpl.java:43)
      	at java.lang.reflect.Method.invoke(Method.java:606)
      	at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:36)
      	... 223 more
      Caused by: java.lang.NullPointerException
      	at org.terracotta.context.extractor.ObjectContextExtractor.extractInstanceAttribute(ObjectContextExtractor.java:57)
      	at org.terracotta.context.extractor.ObjectContextExtractor.extract(ObjectContextExtractor.java:50)
      	at org.terracotta.context.ContextManager.getOrCreateTreeNode(ContextManager.java:129)
      	at org.terracotta.context.ContextManager.associate(ContextManager.java:114)
      	at org.terracotta.context.ContextManager.access$000(ContextManager.java:39)
      	at net.sf.ehcache.constructs.EhcacheDecoratorAdapter.<init>(EhcacheDecoratorAdapter.java:68)
      	at net.sf.ehcache.constructs.blocking.BlockingCache.<init>(BlockingCache.java:93)
      	at net.sf.ehcache.constructs.blocking.BlockingCache.<init>(BlockingCache.java:106)

      Expected result

      No error is thrown.

      Note

      The above error has been resolved in Service Desk 2.5.3 and Atlassian Cache update is required to complement the fix.

            Assignee:
            Oswaldo Hernandez (Inactive)
            Reporter:
            Zul NS [Atlassian] (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: