Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-43159

maven-spy log contains invalid XML

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • pipeline-maven-plugin
    • None
    • Java 8
      Maven 3.3
      Jenkins 2.51
      Pipeline 2.5
      Pipeline Maven Integration Plugin 2.0

    Description

      Our maven-spy-*.log file is being generated with broken XML, for example:

      ...
<ExecutionEvent type=">
<ExecutionEventProjectStarted" class=" type="org.apache.maven.lifecycle.internal.DefaultExecutionEvent" _time="ProjectStarted"2017-03-28 12:05:43.464">
...

      This happens with other elements too; in this particular case, re-running the job leads to exactly the same malformed XML.

      This ultimately leads to an error:

      ERROR: [withMaven] WARNING Exception parsing the logs generated by the Jenkins Maven Event Spy /media/ephemeral0/jenkins/workspace/iMain-Pipeline_release_1.44-HEHP3JF3JUC3QDIC42A5YMRMVQTJR3HJ4P7IFHLSMEGVJNWC55SA@tmp/withMaven21be2166/maven-spy-20170328-094339-928.log, ignore file.  Please report a bug associated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org 
ERROR: org.xml.sax.SAXParseException; lineNumber: 246; columnNumber: 16; Element type "ExecutionEvent" must be followed by either attribute specifications, ">" or "/>".

       

      Attachments

        Issue Links

          is blocked by

          Task - A task that needs to be done. JENKINS-43449 Ensure that the maven-events-spy is thread safe

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-60093 WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Activity

            Ascending order - Click to sort in descending order
            ollierob Ollie Robertshaw added a comment -

            Attached log up to the failure. Afterwards would maybe require too much work to sanitize.

            ollierob Ollie Robertshaw added a comment - Attached log up to the failure. Afterwards would maybe require too much work to sanitize.
            markl_lagendijk Mark Lagendijk added a comment -

            We get similar errors.

            ERROR: [withMaven] WARNING Exception parsing the logs generated by the Jenkins Maven Event Spy /jenkins/workspace/on-release-pipeline_default-NBGOU47BBMAZ5ABRJSVGTSNLZCN3OA3VERV7IMJUQOJD2Q6NM26Q@tmp/withMavencf140cfe/maven-spy-20170406-225029-245.log, ignore file.  Please report a bug associated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org
            ERROR: org.xml.sax.SAXParseException; lineNumber: 196; columnNumber: 2; The content of elements must consist of well-formed character data or markup.

            ERROR: [withMaven] WARNING Exception parsing the logs generated by the Jenkins Maven Event Spy /jenkins/workspace/on-release-pipeline_default-NBGOU47BBMAZ5ABRJSVGTSNLZCN3OA3VERV7IMJUQOJD2Q6NM26Q@tmp/withMaven31a14318/maven-spy-20170406-232907-99.log, ignore file.  Please report a bug associated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org
            ERROR: org.xml.sax.SAXParseException; lineNumber: 163; columnNumber: 6; The value of attribute "_time" associated with an element type "ExecutionEvent" must not contain the '<' character.

            ERROR: [withMaven] WARNING Exception parsing the logs generated by the Jenkins Maven Event Spy /jenkins/workspace/on-release-pipeline_default-NBGOU47BBMAZ5ABRJSVGTSNLZCN3OA3VERV7IMJUQOJD2Q6NM26Q@tmp/withMavena4d8f023/maven-spy-20170406-223923-904.log, ignore file.  Please report a bug associated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org
            ERROR: org.xml.sax.SAXParseException; lineNumber: 152; columnNumber: 8; The content of elements must consist of well-formed character data or markup.

            markl_lagendijk Mark Lagendijk added a comment - We get similar errors. ERROR: [withMaven] WARNING Exception parsing the logs generated by the Jenkins Maven Event Spy /jenkins/workspace/on-release-pipeline_default-NBGOU47BBMAZ5ABRJSVGTSNLZCN3OA3VERV7IMJUQOJD2Q6NM26Q@tmp/withMavencf140cfe/maven-spy-20170406-225029-245.log, ignore file.  Please report a bug associated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org ERROR: org.xml.sax.SAXParseException; lineNumber: 196; columnNumber: 2; The content of elements must consist of well-formed character data or markup. ERROR: [withMaven] WARNING Exception parsing the logs generated by the Jenkins Maven Event Spy /jenkins/workspace/on-release-pipeline_default-NBGOU47BBMAZ5ABRJSVGTSNLZCN3OA3VERV7IMJUQOJD2Q6NM26Q@tmp/withMaven31a14318/maven-spy-20170406-232907-99.log, ignore file.  Please report a bug associated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org ERROR: org.xml.sax.SAXParseException; lineNumber: 163; columnNumber: 6; The value of attribute "_time" associated with an element type "ExecutionEvent" must not contain the '<' character. ERROR: [withMaven] WARNING Exception parsing the logs generated by the Jenkins Maven Event Spy /jenkins/workspace/on-release-pipeline_default-NBGOU47BBMAZ5ABRJSVGTSNLZCN3OA3VERV7IMJUQOJD2Q6NM26Q@tmp/withMavena4d8f023/maven-spy-20170406-223923-904.log, ignore file.  Please report a bug associated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org ERROR: org.xml.sax.SAXParseException; lineNumber: 152; columnNumber: 8; The content of elements must consist of well-formed character data or markup.
            cleclerc Cyrille Le Clerc added a comment -

            This sounds like a thread safety issue. I completely ignored thread safety in the maven-event-spy. I tracked the task in JENKINS-43449

            cleclerc Cyrille Le Clerc added a comment - This sounds like a thread safety issue. I completely ignored thread safety in the maven-event-spy. I tracked the task in JENKINS-43449
            cleclerc Cyrille Le Clerc added a comment -

            Fixed in 2.0.1

            cleclerc Cyrille Le Clerc added a comment - Fixed in 2.0.1
            markl_lagendijk Mark Lagendijk added a comment -

            I can confirm that this is fixed (Y).

            markl_lagendijk Mark Lagendijk added a comment - I can confirm that this is fixed (Y).
            cleclerc Cyrille Le Clerc added a comment -

            Thanks for the great news markl_lagendijk!

            cleclerc Cyrille Le Clerc added a comment - Thanks for the great news markl_lagendijk !

            People

              cleclerc Cyrille Le Clerc
              ollierob Ollie Robertshaw
              Votes:
              3 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: