Tempo Timesheet Exception after Jira Upgrade

Rodrigo Valdés November 16, 2018

Hello 

We are testing Jira Upgrade from Jira 6.x to Jira 7.12.3, Origin Jira  have Tempo Timesheet Plugin version 8.0.4, We installed Tempo Timesheet 8.15.1. However plugin is not working properly since when we try to configure Tempo throws the following Exception.

 

2018-11-16 17:02:12,357 http-nio-18080-exec-6 ERROR admin 1022x3073x1 dtweng 152.139.70.53 /rest/tempo-timesheets/3/timesheet-approval/private/periods-with-pending-approvals [c.a.p.r.c.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: null
java.lang.NullPointerException
at com.tempoplugin.service.period.config.PeriodConfigImpl.getPeriodEndDateByStartDate(PeriodConfigImpl.java:179)
at com.tempoplugin.core.Period.<init>(Period.java:175)
at com.tempoplugin.core.Period.<init>(Period.java:25)
at com.tempoplugin.core.Period$Builder.build(Period.java:53)
at com.tempoplugin.view.TempoViewHelper.getPeriod(TempoViewHelper.java:198)
at com.tempoplugin.view.TempoViewHelper.getPeriod(TempoViewHelper.java:100)
at com.tempoplugin.view.TempoViewHelper.getBillingPeriodForApprovals(TempoViewHelper.java:80)
at com.tempoplugin.view.TempoViewHelper.getPeriodByDate(TempoViewHelper.java:245)
at com.tempoplugin.timesheet.approval.rest.TimesheetApprovalResource.getRecentTimesheetApprovalsForReviewer(TimesheetApprovalResource.java:153)
... 3 filtered
at java.lang.reflect.Method.invoke(Method.java:498)
... 19 filtered
at com.atlassian.plugins.rest.module.RestDelegatingServletFilter$JerseyOsgiServletContainer.doFilter(RestDelegatingServletFilter.java:154)
... 1 filtered
at com.atlassian.plugins.rest.module.RestDelegatingServletFilter.doFilter(RestDelegatingServletFilter.java:68)
... 41 filtered
at com.atlassian.web.servlet.plugin.request.RedirectInterceptingFilter.doFilter(RedirectInterceptingFilter.java:21)
... 53 filtered
at com.atlassian.jira.security.JiraSecurityFilter.lambda$doFilter$0(JiraSecurityFilter.java:66)
... 1 filtered
at com.atlassian.jira.security.JiraSecurityFilter.doFilter(JiraSecurityFilter.java:64)
... 16 filtered
at com.atlassian.plugins.rest.module.servlet.RestSeraphFilter.doFilter(RestSeraphFilter.java:37)
... 19 filtered
at com.atlassian.jira.servermetrics.CorrelationIdPopulatorFilter.doFilter(CorrelationIdPopulatorFilter.java:30)
... 10 filtered
at com.atlassian.web.servlet.plugin.request.RedirectInterceptingFilter.doFilter(RedirectInterceptingFilter.java:21)
... 4 filtered
at com.atlassian.web.servlet.plugin.LocationCleanerFilter.doFilter(LocationCleanerFilter.java:36)
... 26 filtered
at com.atlassian.jira.servermetrics.MetricsCollectorFilter.doFilter(MetricsCollectorFilter.java:25)
... 24 filtered
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)
2018-11-16 17:29:39,228 Caesium-1-3 DEBUG ServiceRunner [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] getService bundle [com.atlassian.plugins.authentication.atlassian-authentication-plugin]

 

Any idea how to get plugin to work properly.?

 

Thanks in advance.

Best Regards

 

 

3 answers

0 votes
feng liu December 19, 2019

API problem:/rest/tempo-timesheets/4/period-configuration,update the configuration,I resolve it!

0 votes
Erick Johanson December 1, 2019

It was fixed? We have  little similar issue, we cant access the page with period configuration and when we try to open timesheets we got "something goes wrong"

 

/rest/tempo-timesheets/4/timesheet-approval/approval-statuses [c.a.p.r.c.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: The default period configuration was not found.
java.lang.IllegalArgumentException: The default period configuration was not found.
at com.tempoplugin.worklog.v4.services.PeriodConfigurationFactoryImpl.getDefaultPeriodConfiguration(PeriodConfigurationFactoryImpl.java:42)
at com.tempoplugin.worklog.v4.services.PeriodConfigurationFactoryImpl.getForApprovals(PeriodConfigurationFactoryImpl.java:30)
at com.tempoplugin.timesheet.approval.v4.services.PeriodFactoryImpl.createApprovalPeriodConfiguration(PeriodFactoryImpl.java:52)
at com.tempoplugin.timesheet.approval.v4.services.PeriodFactoryImpl.createPeriods(PeriodFactoryImpl.java:48)
at com.tempoplugin.timesheet.approval.v4.services.ApprovalV3ResourceBridge.createPeriods(ApprovalV3ResourceBridge.java:348)
at com.tempoplugin.timesheet.approval.v4.services.ApprovalV3ResourceBridge.getTimesheetApprovalsForUserOverMultiplePeriods(ApprovalV3ResourceBridge.java:282)

Susanne Götz _Tempo_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 2, 2019

Hi @Erick Johanson 

 

Can you please create a ticket for this in our Tempo support system (https://tempo-io.atlassian.net/servicedesk/customer/portal/6) so we can better investigate this problem. 

It looks like it might be caused by an upgrade task that did not run correctly. 
If you were recently updating Tempo, can you please add information about the versions you were using before and which version you were updating to. 
The support zip file might also be helpful (https://confluence.atlassian.com/support/create-a-support-zip-790796819.html).

Regards
Susanne Götz
Tempo team 

0 votes
Susanne Götz _Tempo_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 19, 2018

Hi Rodrigo,

 

Can you please inform us if you were following the update procedure as described on https://tempo-io.atlassian.net/wiki/spaces/TEMPO/pages/277971066/To+prepare+to+update+Tempo+Timesheets+for+Server when updating Tempo.

The error you receive looks like an upgrade task did not run correctly. This can happen when you are updating directly from Tempo Timesheets 8.0.4 to the latest version. In that case, can you please create a ticket in our Tempo support (https://tempo-io.atlassian.net/servicedesk/customer/portal/6) so we can better assist you with fixing this problem.

Regards,
Susanne Götz
Tempo team

Adam Martin February 27, 2019

Susanne, could you please explain this issue, and possible steps for resolution.  I have hit this same stack trace and can't figure out why.

We have restored an instance to a docker platform for testing merge migrations.  No version changes in the process, and selecting "Timesheets" leads to this error.

I've also notice the period configuration in the Jira add-on admin results in a blank screen without errors.

Thanks!

Adam Martin
Isos Technology

Susanne Götz _Tempo_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 28, 2019

Hi @Adam Martin 

It might be useful to create a ticket for this in our Tempo support so we can better follow up on this.

Please add the versions of JIRA and Tempo you are using and the steps you have taken when restoring.

Regards,

Susanne

Richard Duffy July 20, 2020

HI Guys

Also have the blank period configuration page, what was the resolution?

Suggest an answer

Log in or Sign up to answer