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

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問


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.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Fisheye および Crucible は除く

問題

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)

診断

環境

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

回避策

Perform reindexing and JIRA restart.

最終更新日 2018 年 11 月 2 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.