[NIFI-8417] emoji in processor group name cause nifi to not start up

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.13.0, 1.13.1, 1.13.2
• Fix Version/s: 1.14.0
• Component/s: Core Framework
• Environment: RHEL 7, jdk8
• Assignee: Hsin-Ying Lee
• Reporter: Adam Turley
• Created: 12/Apr/21 16:18
• Updated: 01/Sep/21 14:58
• Resolved: 11/May/21 13:29

Description

if a processor group includes an emoji in the name, nifi will work normally until restart. Once restarted nifi will endlessly crash with the following error message:

2021-04-12 16:06:56,100 ERROR [main] org.apache.nifi.web.server.JettyServer Unable to load flow due to: org.apache.nifi.controller.serialization.FlowSerializationException: org.xml.sax.SAXParseException; lineNumber: 341336; columnNumber: 21; Character reference "&#55356" is an invalid XML character.
org.apache.nifi.controller.serialization.FlowSerializationException: org.xml.sax.SAXParseException; lineNumber: 341336; columnNumber: 21; Character reference "&#55356" is an invalid XML character.
at org.apache.nifi.cluster.protocol.StandardDataFlow.parseFlowBytes(StandardDataFlow.java:136)
at org.apache.nifi.cluster.protocol.StandardDataFlow.getFlowDocument(StandardDataFlow.java:96)
at org.apache.nifi.controller.StandardFlowSynchronizer.sync(StandardFlowSynchronizer.java:185)
at org.apache.nifi.controller.FlowController.synchronize(FlowController.java:1413)
at org.apache.nifi.persistence.StandardXMLFlowConfigurationDAO.load(StandardXMLFlowConfigurationDAO.java:89)
at org.apache.nifi.controller.StandardFlowService.loadFromBytes(StandardFlowService.java:810)
at org.apache.nifi.controller.StandardFlowService.load(StandardFlowService.java:458)
at org.apache.nifi.web.server.JettyServer.start(JettyServer.java:1133)
at org.apache.nifi.NiFi.<init>(NiFi.java:159)
at org.apache.nifi.NiFi.<init>(NiFi.java:71)
at org.apache.nifi.NiFi.main(NiFi.java:303)
Caused by: org.xml.sax.SAXParseException: Character reference "&#55356" is an invalid XML character.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)
at org.apache.xerces.impl.XMLScanner.scanCharReferenceValue(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanCharReference(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121)
at org.apache.nifi.cluster.protocol.StandardDataFlow.parseFlowBytes(StandardDataFlow.java:134)
... 10 common frames omitted

Issue Links

• links to: GitHub Pull Request #5012