Service Management fails to Load Queue with datetime Exception

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

When attempting to load a queue in Service Management, it fails with Error code: ERR_CONTENT_DECODING_FAILED

The following appears in the atlassian-jira.log:

2014-02-24 15:51:08,999 JiraTaskExectionThread-1 ERROR admin 1079x731x1 1xwufci 0:0:0:0:0:0:0:1 /rest/servicedesk/1/servicedesk [servicedesk.internal.util.SafeRunner] Unable to run event handler SLA field indexing - addDocumentFieldsSearchable
java.lang.IllegalArgumentException: The datetime zone id 'GMT-07:00' is not recognised
	at org.joda.time.DateTimeZone.forID(DateTimeZone.java:223)
	at com.atlassian.jira.plugins.workinghours.internal.calculator.WorkingHoursCalculatorServiceImpl.getAlwaysOnCalculator(WorkingHoursCalculatorServiceImpl.java:38)
	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 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 org.springframework.osgi.service.util.internal.aop.ServiceTCCLInterceptor.invokeUnprivileged(ServiceTCCLInterceptor.java:56)
	at org.springframework.osgi.service.util.internal.aop.ServiceTCCLInterceptor.invoke(ServiceTCCLInterceptor.java:39)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
	at org.springframework.osgi.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:59)
	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 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
	at com.sun.proxy.$Proxy2178.getAlwaysOnCalculator(Unknown Source)
	at com.atlassian.servicedesk.internal.sla.configuration.calendar.CalendarReferenceManagerImpl.getDefaultCalculator(CalendarReferenceManagerImpl.java:99)
	at com.atlassian.servicedesk.internal.sla.configuration.calendar.CalendarReferenceManagerImpl.getCalculatorForReference(CalendarReferenceManagerImpl.java:79)Diagnosis

Looking at Jira's startup logs shows this parameter:

     user.timezone                                 : GMT-07:00

Cause

The timezone value will be picked up by default from the operating system. In some cases, commonly on Windows, the provided format is not in a parseable format.

Resolution

Modify the timezone as per our Setting the timezone for the JAVA environment KB article, for example -Duser.timezone=America/Los_Angeles

Last modified on Nov 23, 2020

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.