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

Maven Event Spy seems to still have a thread safe problem

      Exception:

      ERROR: [withMaven] WARNING Exception parsing the logs generated by the Jenkins Maven Event Spy /var/lib/jenkins/workspace/_appia=gui/F__appia_-_gui_-_master@tmp/withMaven1afdee4c/maven-spy-20170831-215714-662.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: 3824; columnNumber: 53; XML document structures must start and end within the same entity.
      

          [JENKINS-46579] Maven Event Spy seems to still have a thread safe problem

          Code changed in jenkins
          User: Alvaro Lobato
          Path:
          maven-spy/src/main/java/org/jenkinsci/plugins/pipeline/maven/eventspy/reporter/FileMavenEventReporter.java
          maven-spy/src/test/java/org/jenkinsci/plugins/pipeline/maven/eventspy/JenkinsMavenEventSpyMTTest.java
          http://jenkins-ci.org/commit/pipeline-maven-plugin/810fe9a4c7a61c4c7ccb7a35636811e22d437480
          Log:
          JENKINS-46579 - Concurrency problems with spy log (#91)

          JENKINS-46579 maven event spy: Fix concurrency issue in the handling of the output file

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Alvaro Lobato Path: maven-spy/src/main/java/org/jenkinsci/plugins/pipeline/maven/eventspy/reporter/FileMavenEventReporter.java maven-spy/src/test/java/org/jenkinsci/plugins/pipeline/maven/eventspy/JenkinsMavenEventSpyMTTest.java http://jenkins-ci.org/commit/pipeline-maven-plugin/810fe9a4c7a61c4c7ccb7a35636811e22d437480 Log: JENKINS-46579 - Concurrency problems with spy log (#91) JENKINS-46579 maven event spy: Fix concurrency issue in the handling of the output file

          FYI I have created JENKINS-46609 . pino could the Maven process could have been killed by the operating system? I saw this problem in docker/cgroup environments.

          Cyrille Le Clerc added a comment - FYI I have created JENKINS-46609 . pino could the Maven process could have been killed by the operating system? I saw this problem in docker/cgroup environments.

          Well well, that was it. The maven process was getting killed for no apparent reason. I played with the java Xmx and it looks much better now. I don't understand why it would fail with Xmx3G when in dev we use Xmx2G but I have increased this to 4G and it seems to work.

          Pino Silvaggio added a comment - Well well, that was it. The maven process was getting killed for no apparent reason. I played with the java Xmx and it looks much better now. I don't understand why it would fail with Xmx3G when in dev we use Xmx2G but I have increased this to 4G and it seems to work.

          Can you clarify which Xmx you are referring to?
          Do you run this process in a Docker container or in cgroups?
          Do the memory of this agents fits with the sumof the memory of all the known processes ? Slave.jar + mvn process + maybe mvn sub processes
          Can you monitor the memory, CPU and load of this agent to detect problems?

          Cyrille Le Clerc added a comment - Can you clarify which Xmx you are referring to? Do you run this process in a Docker container or in cgroups? Do the memory of this agents fits with the sumof the memory of all the known processes ? Slave.jar + mvn process + maybe mvn sub processes Can you monitor the memory, CPU and load of this agent to detect problems?

          Cyrille Le Clerc added a comment - - edited

          Fixed by https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/pipeline-maven/3.0.1-beta-1/pipeline-maven-3.0.1-beta-1.hpi
          We detect when the Maven build has been killed and don't display this confusing XML parsing exception. See Pipeline Maven Plugin> Why do I see messages...

          Cyrille Le Clerc added a comment - - edited Fixed by https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/pipeline-maven/3.0.1-beta-1/pipeline-maven-3.0.1-beta-1.hpi We detect when the Maven build has been killed and don't display this confusing XML parsing exception. See Pipeline Maven Plugin> Why do I see messages...

          Cyrille Le Clerc added a comment - pino could you test the 3.0.1-beta? https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.0.1-beta-2

          I will, I am however on vacation at this time.

          Pino Silvaggio added a comment - I will, I am however on vacation at this time.

          Thanks pino, as I have already tested, we may release before you are back from holidays

          Cyrille Le Clerc added a comment - Thanks pino , as I have already tested, we may release before you are back from holidays

          v3.0.1

          Cyrille Le Clerc added a comment - v3.0.1

          we run version 3.6.11 and still see this from time to time:

           

          ERROR: [withMaven] WARNING Exception parsing the logs generated by the Jenkins Maven Event Spy /home/ec2-user/workspace/org_yooture_develop@tmp/withMaven5705f0d0/maven-spy-20190520-135648-9715492809875305253764.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: 18407; columnNumber: 263; XML document structures must start and end within the same entity. 

          Dominik Bartholdi added a comment - we run version 3.6.11 and still see this from time to time:   ERROR: [withMaven] WARNING Exception parsing the logs generated by the Jenkins Maven Event Spy /home/ec2-user/workspace/org_yooture_develop@tmp/withMaven5705f0d0/maven-spy-20190520-135648-9715492809875305253764.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: 18407; columnNumber: 263; XML document structures must start and end within the same entity.

            Unassigned Unassigned
            pino Pino Silvaggio
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: