Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
2
-
Description
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Following warning is dropped into log file due to misbehaving plugin.
2011-02-17 09:39:12,163 http-8080-5 WARN xxxxxxx 579x6004x1 1b7w9ft 192.179.113.217 /secure/IssueNavigator.jspa [velocity] org.apache.velocity.runtime.exception.ReferenceException: reference : template = getEncodedBodyFromContent [line 1,column 71] : ${issue.id} is not a valid reference. at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:277) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230) at org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300) at org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202) at com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143) at com.atlassian.jira.plugin.webfragment.JiraWebFragmentHelper.getHtml(JiraWebFragmentHelper.java:115)
It would be nice if JIRA could capture info about the offending plugin and log it.
Based on Jeremy's and customers feedback from our KB page - Is Not a Valid Reference Error.
Attachments
Issue Links
- relates to
-
JRACLOUD-25195 Capture offending plugin causing 'issue.id is not a valid reference' error
- Closed
- mentioned in
-
Page Loading...