[TIME-56] Missing hours for issues in the timesheet

[Andriy Zhdanov]

Hi,

Error periodically appears in the timesheet portlet which does not show the hours logged for each issue however it does show the issue itself as well as the total hours (does not show the hours for each individual issue). This issue seems to come and go without warning.

When examining the log files for JIRA, we identified the following stacktrace:

2009-01-14 16:25:40,711 http-80-Processor7 ERROR velocity RHS of #set statement is null. Context will not be modified. templates/timesheetportlet/timesheet
-entry.vm line 23, column 9
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)

We are currently using version 1.8 of the plugin .

Please let us know what is causing this problem and if there are any workarounds as sometimes this error hangs around for a couple days, which affects our users and managers greatly.

Regards,
Sarhang

By sarhang/Sarhang Hevary on Thu, 15 Jan 2009 02:04:14 -0800

[Andriy Zhdanov]

The error is abnormal:

2009-01-14 16:25:40,711 http-80-Processor7 ERROR velocity RHS of #set statement is null. Context will not be modified. templates/timesheetportlet/timesheet-entry.vm line 23, column 9

If you look at the code, there at templates\timesheetportlet\timesheet-entry.vm line 23 is the following:

#set ($timespents = $weekWorkLog.get($issue))

But $weekWorkLog map key $issue is obtained earlier in templates\timesheetportlet\timesheet-portlet.vm from the map with keySet() method:

#set ($worklogKeys = $weekWorkLog.keySet())
#foreach ($issue in $worklogKeys)
#parse('templates/timesheetportlet/timesheet-entry.vm')
#end

And I can not imagine how map may contain null element, since map is filled in report\timesheet\TimeSheet.java:
Map weekTimeSpents = (Map) weekWorkLogShort.get(issue);
if (weekTimeSpents == null) { weekTimeSpents = new Hashtable(); weekWorkLogShort.put(issue, weekTimeSpents); // portlet }

I.e. new element is added right after its initialization.

I have some diagnostic questions:
1. What does mean "error appears periodically", does it disappear if you refresh page, or it is persistent for some time, is it regular somehow?
2. When the error occurs do you see the same at timesheet Report, if you click Details at portlet?
3. Which Java do you use?
4. Would you like me to send you custom version of plugin with more debug logging for diagnostics?

By azhdanov on Sat, 14 Feb 2009 10:43:09 -0800

[Andriy Zhdanov]

Assuming resolved, as no response

By azhdanov on Sat, 16 May 2009 08:15:45 -0700

[Andriy Zhdanov]

We are observing much the same - running a user's time tracking report (TIME 1.8 with Jira 3.13.5) covering a five month period produces tens of thousands of errors in the log while Jira grinds to a halt. These errors are of the nature of:

2009-12-01 10:29:20,535 TP-Processor1 ERROR velocity RHS of #set statement is null. Context will not be modified. templates/timesheetreport/timesheet-report-project-totals.vm line 14, column 8
2009-12-01 10:29:21,091 TP-Processor1 ERROR velocity RHS of #set statement is null. Context will not be modified. templates/timesheetreport/timesheet-report-project-totals.vm line 14, column 8

Eventually leading to:

java.lang.OutOfMemoryError: Java heap space

By charlesa on Wed, 2 Dec 2009 00:52:43 -0800

[Andriy Zhdanov]

I resolved the symptom of this by disabling the profiling in "Logging and Profiling" administrator's console.

Tested enabling/disabling and the "ERROR velocity RHS of #set statement..." symptom is assured. Data is properly shown in the Project Timesheet report and even the excel export resumes normal functioning (It had stopped working. Returned an empty sheet instead)

I can't answer the reason of the link between the profiler and the error in the timesheet reports though.

We make use of this plugin and I'd appreciate this bug is reopened despite the error can be kind of worked around.

By jramirez on Mon, 22 Feb 2010 05:02:54 -0800