Jelly Service does not work with 'Could not read script string'
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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.
*Except Fisheye and Crucible
Symptoms
When trying to run the Jelly Service, the following appears in the atlassian-jira.log:
1
2
3
4
5
6
7
8
9
10
11
2011-11-16 15:18:26,600 ajp-8009-1 ERROR df 918x4418x1 1j1r725 172.28.1.71 /secure/admin/util/JellyRunner.jspa [web.action.util.JellyRunner] Could not read script string.
java.io.IOException: expected '=', got 'x'
at electric.util.lex.Lex.readChar(Lex.java:371)
at electric.xml.sax.SAXParser.parseAttributes(SAXParser.java:685)
at electric.xml.sax.SAXParser.parseElement(SAXParser.java:597)
at electric.xml.sax.SAXParser.parse(SAXParser.java:330)
at electric.xml.sax.SAXParser.parse(SAXParser.java:270)
at electric.xml.sax.SAXParser.parse(SAXParser.java:241)
at electric.xml.sax.SAXParser.parse(SAXParser.java:207)
at org.apache.commons.jelly.parser.XMLParser.parse(XMLParser.java:238)
at org.apache.commons.jelly.parser.XMLParser.parse(XMLParser.java:220)Cause
The Jelly script file does not work with UTF-8 encoding (tested in JIRA 4.4.3).
Resolution
Save the file in 'UTF-8 without BOM' encoding
Was this helpful?