[TIME-37] Excessive template warnings in logs
In both 1.7 and 1.8 we are getting excessive warnings in the log when at DEBUG level. Just thought you might want to know that these show up constantly and fill the debug log when we are troubleshooting issues:
2008-03-10 17:32:22,578 http-80-Processor25 WARN velocity Warning! The iterative is an Iterator in the #foreach() loop at 0,0 in template templates/timesheetreport/timesheet-entry.vm. Because it's not resetable, if used in more than once, this may lead to unexpected results.
2008-03-10 17:32:22,578 http-80-Processor25 WARN velocity Warning! The iterative is an Iterator in the #foreach() loop at 0,0 in template templates/timesheetreport/timesheet-entry.vm. Because it's not resetable, if used in more than once, this may lead to unexpected results.
2008-03-10 17:32:22,750 http-80-Processor25 WARN velocity Warning! The iterative is an Iterator in the #foreach() loop at 0,0 in template templates/timesheetreport/timesheet-entry.vm. Because it's not resetable, if used in more than once, this may lead to unexpected results.
2008-03-10 17:32:22,891 http-80-Processor25 WARN velocity Warning! The iterative is an Iterator in the #foreach() loop at 0,0 in template templates/timesheetreport/timesheet-entry.vm. Because it's not resetable, if used in more than once, this may lead to unexpected results.
2008-03-10 17:32:23,063 http-80-Processor25 WARN velocity Warning! The iterative is an Iterator in the #foreach() loop at 0,0 in template templates/timesheetreport/timesheet-entry.vm. Because it's not resetable, if used in more than once, this may lead to unexpected results.
2008-03-10 17:32:23,235 http-80-Processor25 WARN velocity Warning! The iterative is an Iterator in the #foreach() loop at 0,0 in template templates/timesheetreport/timesheet-entry.vm. Because it's not resetable, if used in more than once, this may lead to unexpected results.
By mattyj2001/Matthew Janulewicz on Mon, 10 Mar 2008 19:42:08 -0700
Comments (1)
-
reporter - Log in to comment
This message appears because of nested loops, that are needed to render the reports, I can't rework plugin to avoid this messages.
You may suppress the messages. Edit <JIRA_HOME>/WEB-INF/classes/log4j.properties, add the following lines mostly in the end, before THREAD LOCAL ERROR LOG APPENDER:
log4j.category.velocity = ERROR, console, filelog
log4j.additivity.category.velocity = false
By azhdanov on Tue, 11 Mar 2008 02:08:47 -0700