org.apache.velocity.exception.ParseErrorException error message after JIRA upgrade

Still need help?

The Atlassian Community is here for you.

Ask the community


Platform Notice: Server, Data Center, and Cloud By Request - This article was written for the Atlassian server and data center platforms but may also be useful for Atlassian Cloud customers. If completing instructions in this article would help you, please contact Atlassian Support and mention it.

Problem

User will keep getting this message in the browser page:

An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- org.apache.velocity.exception.ParseErrorException: Encountered "#end\n" at getEncodedBodyFromContent[line 68, column 1] Was expecting one of: <EOF> "(" ... <RPAREN> ... <ESCAPE_DIRECTIVE> ... <SET_DIRECTIVE> ... "##" ... "\\\\" ... "\\" ... <TEXT> ... "*#" ... "*#" ... <STRING_LITERAL> ... <IF_DIRECTIVE> ... <STOP_DIRECTIVE> ... <INTEGER_LITERAL> ... <FLOATING_POINT_LITERAL> ... <WORD> ... <BRACKETED_WORD> ... <IDENTIFIER> ... <DOT> ... "{" ... "}" ... 
at org.apache.velocity.runtime.RuntimeInstance.evaluate(RuntimeInstance.java:1202) 
at org.apache.velocity.runtime.RuntimeInstance.evaluate(RuntimeInstance.java:1164) 
at org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:219) 
at com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:205) 
at com.javahollic.jira.emh.service.DefaultJEMHMessageManager.createDefaultJiraUserEmail(DefaultJEMHMessageManager.java:1735) 
at com.javahollic.jira.emh.service.DefaultJEMHMessageManager.createJiraUserEmail(DefaultJEMHMessageManager.java:2041) 
at com.javahollic.jira.emh.service.DefaultJEMHMessageManager.createJiraUserEmail(DefaultJEMHMessageManager.java:1789) 
at com.javahollic.jira.emh.service.listener.JiraUserNotifier.handleNotification(JiraUserNotifier.java:186) 
at com.javahollic.jira.emh.service.listener.JEMHIssueEventListener.handleEmailNotifications(JEMHIssueEventListener.java:299) 
at com.javahollic.jira.emh.service.listener.JEMHIssueEventListener.onIssueEvent(JEMHIssueEventListener.java:152) 
at sun.reflect.GeneratedMethodAccessor2106.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
at java.lang.reflect.Method.invoke(Method.java:497) 
at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:36) 
at com.atlassian.event.internal.AsynchronousAbleEventDispatcher$1$1.run(AsynchronousAbleEventDispatcher.java:48)

Diagnosis

Environment

  • After completed JIRA Upgrade from 6.2.x to 6.4.x

Workaround

Perform reindexing and JIRA restart.

Last modified on Nov 2, 2018

Was this helpful?

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