-
Type:
Bug
-
Resolution: Low Engagement
-
Priority:
Low
-
None
-
Affects Version/s: 7.1.4
-
Component/s: Navigation - Export
-
7.01
-
8
-
Severity 3 - Minor
-
0
Summary
As per Removing invalid characters from XML backups, JIRA 3.1 and above should not suffer from this problem unless migrating to postgreSQL from another database such as MySQL. Invalid characters otherwise are automatically stripped from imported data. But, even from the same database, the XML backup that is being generated still have invalid characters which are breaking the XML file.
Environment
MySQL DBMS with utf8-bin.
Steps to Reproduce
- Fresh vanilla JIRA 7.1.4 instance.
- Paste this into an issue description or comment:
at XXX.Enabler.WebHost.Program.()
at XXX.Enabler.WebHost.Program.(String[] )11:45:35.761 Log event 16 device 10 number 3 [Age 4 dur 158614805 try 0oo)oo oLooGo o+o'oBo o o.o1o&o2oqo0oÿÿJo(o-o*o6o,o=o3o7oro÷o9oEo@o8oÿÿÿÿNo:o;oQoAo?oùoIoÙoDoWoOoFoÿÿKoko€oiofoVomoPoƒoÿÿToSoRoZoUo\o]oXoaoeo^oÿÿcoÿÿ_odo`onoboyoho|o}o„o˜oÿÿooloûo‚o—o“oxopozoÅosotouovowo{oo‰oo~oˆoŠošo…oo†o¥oµoŽo‡oŒo‹o•ooŸooÿÿ‘o¢o´o o–o”oºoo¦oœo³o™oÀo›ožo¡o£oo©o¨o¤o¶oªo§o»o²o«o¼o¸o¯o¬o°o®o±o½o¹oÒoÄoÝo·oäoÈoíoÉoÿÿÞoÌoÆoÂo¿oÁoãoÃoÇoÊoÎop×oÏoØoÐoËoÍoàoÔoÛoÑoæoÜoÓoÖoÕoÚoðoâoêopßoëoéoþoáoçop/pòoåo p pôoèoìoîoüoöoóoïoõo$pño*ppøopýopÿÿúo¢p11:46:26.933 Pump 27 LOCKED_PSTATE Hose=-1 lastState=10 ReservedState=1
Paste this in Sublime and you will see the special characters. - Generate a XML backup.
- Unzip the backup file and validate the entities.xml file:
xmllint entities.xml
Expected Results
The entities.xml should be generated as a valid XML file.
Actual Results
The result of xmllint entities.xml:
entities.xml:XXXXX: parser error : CData section not finished
Problem was actually caused by exception in EnbWeb
at XXX.Enabler.WebHost.Program.()
^
entities.xml:XXXXX: parser error : PCDATA invalid Char value 2
at XXX.Enabler.WebHost.Program.()
^
entities.xml:XXXXX: parser error : PCDATA invalid Char value 1
at XXX.Enabler.WebHost.Program.(String[] )
^
entities.xml:XXXXX: parser error : PCDATA invalid Char value 1
at XXX.Enabler.WebHost.Program.(String[] )
^
entities.xml:XXXXX: parser error : Sequence ']]>' not allowed in content
]]></body>
^
entities.xml:XXXXX: parser error : CData section not finished
*ID:003, IP:163* Start From 03/27
# Pump Server s
noformat}11:45:35.761 Log event 16 device 10 number 3 [Age 4 dur 158614805 try 0
^
entities.xml:XXXXX: parser error : PCDATA invalid Char value 17
noformat}11:45:35.761 Log event 16 device 10 number 3 [Age 4 dur 158614805 try 0
^
entities.xml:XXXXX: parser error : PCDATA invalid Char value 19
format}11:45:35.761 Log event 16 device 10 number 3 [Age 4 dur 158614805 try 0o
^
entities.xml:XXXXX: parser error : PCDATA invalid Char value 24
at}11:45:35.761 Log event 16 device 10 number 3 [Age 4 dur 158614805 try 0oo)o
^
entities.xml:XXXXX: parser error : PCDATA invalid Char value 23
45:35.761 Log event 16 device 10 number 3 [Age 4 dur 158614805 try 0oo)oo oLo
^
entities.xml:XXXXX: parser error : PCDATA invalid Char value 28
5.761 Log event 16 device 10 number 3 [Age 4 dur 158614805 try 0oo)oo oLooGo
^
entities.xml:XXXXX: parser error : PCDATA invalid Char value 29
g event 16 device 10 number 3 [Age 4 dur 158614805 try 0oo)oo oLooGoo+o'oBo
^
entities.xml:XXXXX: parser error : PCDATA invalid Char value 30
event 16 device 10 number 3 [Age 4 dur 158614805 try 0oo)oo oLooGoo+o'oBoo
^
entities.xml:XXXXX: parser error : EntityRef: expecting ';'
umber 3 [Age 4 dur 158614805 try 0oo)oo oLooGoo+o'oBooo.o1o&o2oqo0oÿÿJo
^
entities.xml:XXXXX: parser error : PCDATA invalid Char value 22
o¬o°o®o±o½o¹oÒoÄoÝo·oäoÈoíoÉoÿÿÞoÌoÆoÂo¿oÁoãoÃoÇoÊoÎo
^
entities.xml:XXXXX: parser error : PCDATA invalid Char value 1
p×oÏoØoÐoËoÍoàoÔoÛoÑoæoÜoÓoÖoÕoÚoðoâoêo�pßoëoéoþoáoço
^
entities.xml:XXXXX: parser error : PCDATA invalid Char value 28
oÐoËoÍoàoÔoÛoÑoæoÜoÓoÖoÕoÚoðoâoêo�pßoëoéoþoáoçop/pòoåo
^
entities.xml:XXXXX: parser error : PCDATA invalid Char value 3
▒oðoâoêo�pßoëoéoþoáoçop/pòoåop pôoèoìoîoüoöoóoïoõo$pño*p
^
entities.xml:XXXXX: parser error : PCDATA invalid Char value 2
âoêo�pßoëoéoþoáoçop/pòoåop pôoèoìoîoüoöoóoïoõo$pño*ppøo
^
entities.xml:XXXXX: parser error : PCDATA invalid Char value 6
o�pßoëoéoþoáoçop/pòoåop pôoèoìoîoüoöoóoïoõo$pño*ppøopýo
^
entities.xml:XXXXX: parser error : Sequence ']]>' not allowed in content
11:46:26.967 CStatusChangeEvent Pump:23 Type:0 Value1:4 Value2:1
Workaround
The workaround is to clean the XML file; Removing invalid characters from XML backups.