org.xml.sax.SAXParseException: The entity name must immediately follow the '&' in the entity reference.

Jenkins JIRA | jeffolson | 8 years ago
  1. 0

    When a TFS changeset has an ampersand (&) character in the comment, the TFS plugin gets a "Parse Fatal Error" resulting from a SAXParseException. The result of this is that no changes are shown for the build in the Hudson UI, even though TFS changesets were found. Here is an example stacktrace: SEVERE: Parse Fatal Error at line 6 column 54: The entity name must immediately follow the '&' in the entity reference. org.xml.sax.SAXParseException: The entity name must immediately follow the '&' in the entity reference. 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.XMLScanner.reportFatalError(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEntityReference(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.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.apache.commons.digester.Digester.parse(Digester.java:1685) at hudson.plugins.tfs.ChangeSetReader.parse(ChangeSetReader.java:54) at hudson.plugins.tfs.ChangeSetReader.parse(ChangeSetReader.java:31) at hudson.plugins.tfs.ChangeSetReader.parse(ChangeSetReader.java:25) at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:429) at hudson.model.AbstractBuild.access$500(AbstractBuild.java:78) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:320) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:266) at hudson.model.Run.run(Run.java:927) at hudson.model.Build.run(Build.java:112) at hudson.model.ResourceController.execute(ResourceController.java:93) at hudson.model.Executor.run(Executor.java:119) org.xml.sax.SAXParseException: The entity name must immediately follow the '&' in the entity reference. at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.apache.commons.digester.Digester.parse(Digester.java:1685) at hudson.plugins.tfs.ChangeSetReader.parse(ChangeSetReader.java:54) at hudson.plugins.tfs.ChangeSetReader.parse(ChangeSetReader.java:31) at hudson.plugins.tfs.ChangeSetReader.parse(ChangeSetReader.java:25) at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:429) at hudson.model.AbstractBuild.access$500(AbstractBuild.java:78) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:320) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:266) at hudson.model.Run.run(Run.java:927) at hudson.model.Build.run(Build.java:112) at hudson.model.ResourceController.execute(ResourceController.java:93) at hudson.model.Executor.run(Executor.java:119) Here is an example changeset: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Changeset: 803980 User: U0026729 Date: Tuesday, May 26, 2009 3:35:24 PM Comment: Just testing what happens when I use the & character...Hudson does not seem to like it! Items: add $/Checkpoint/CheckpointWebApp/main/etc/dummy.txt Check-in Notes: Code Reviewer: Performance Reviewer: Security Reviewer: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I'm running Hudson 1.307 with TFS plugin 1.4, on a Windows 2003 SP2 server.

    Jenkins JIRA | 8 years ago | jeffolson
    org.xml.sax.SAXParseException: The entity name must immediately follow the '&' in the entity reference.
  2. 0

    When a TFS changeset has an ampersand (&) character in the comment, the TFS plugin gets a "Parse Fatal Error" resulting from a SAXParseException. The result of this is that no changes are shown for the build in the Hudson UI, even though TFS changesets were found. Here is an example stacktrace: SEVERE: Parse Fatal Error at line 6 column 54: The entity name must immediately follow the '&' in the entity reference. org.xml.sax.SAXParseException: The entity name must immediately follow the '&' in the entity reference. 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.XMLScanner.reportFatalError(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEntityReference(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.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.apache.commons.digester.Digester.parse(Digester.java:1685) at hudson.plugins.tfs.ChangeSetReader.parse(ChangeSetReader.java:54) at hudson.plugins.tfs.ChangeSetReader.parse(ChangeSetReader.java:31) at hudson.plugins.tfs.ChangeSetReader.parse(ChangeSetReader.java:25) at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:429) at hudson.model.AbstractBuild.access$500(AbstractBuild.java:78) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:320) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:266) at hudson.model.Run.run(Run.java:927) at hudson.model.Build.run(Build.java:112) at hudson.model.ResourceController.execute(ResourceController.java:93) at hudson.model.Executor.run(Executor.java:119) org.xml.sax.SAXParseException: The entity name must immediately follow the '&' in the entity reference. at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.apache.commons.digester.Digester.parse(Digester.java:1685) at hudson.plugins.tfs.ChangeSetReader.parse(ChangeSetReader.java:54) at hudson.plugins.tfs.ChangeSetReader.parse(ChangeSetReader.java:31) at hudson.plugins.tfs.ChangeSetReader.parse(ChangeSetReader.java:25) at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:429) at hudson.model.AbstractBuild.access$500(AbstractBuild.java:78) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:320) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:266) at hudson.model.Run.run(Run.java:927) at hudson.model.Build.run(Build.java:112) at hudson.model.ResourceController.execute(ResourceController.java:93) at hudson.model.Executor.run(Executor.java:119) Here is an example changeset: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Changeset: 803980 User: U0026729 Date: Tuesday, May 26, 2009 3:35:24 PM Comment: Just testing what happens when I use the & character...Hudson does not seem to like it! Items: add $/Checkpoint/CheckpointWebApp/main/etc/dummy.txt Check-in Notes: Code Reviewer: Performance Reviewer: Security Reviewer: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I'm running Hudson 1.307 with TFS plugin 1.4, on a Windows 2003 SP2 server.

    Jenkins JIRA | 8 years ago | jeffolson
    org.xml.sax.SAXParseException: The entity name must immediately follow the '&' in the entity reference.
  3. 0

    The Axis Users List

    gmane.org | 5 months ago
    org.xml.sax.SAXParseException: Content is not allowed in prolog. faultActor: faultNode: faultDetail: { Content is not allowed in prolog. at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Re: Portal - Coplets / Sunlet

    apache.org | 1 year ago
    org.xml.sax.SAXParseException: The element type "META" must be terminated by the matching end-tag "". at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHand lerWrapper.java:232) at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.ja va:213) at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:37 5) at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:30 5)
  6. 0

    SAXParseException in Apache HTTP error log file import.

    Eclipse Bugzilla | 1 decade ago | ewchan
    org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x1c) was found in the CDATA section.

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. org.xml.sax.SAXParseException

      The entity name must immediately follow the '&' in the entity reference.

      at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException()
    2. Xerces2-j
      XMLScanner.reportFatalError
      1. org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(UnknownSource)
      2. org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
      3. org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
      4. org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
      5. org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)
      5 frames