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

Sporadic IOException: Failed to persist config

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      When creating the projects, I am getting sporadic failures in the jenkins error log as seen below. Jobs then fail to be updated.

      INFO: createOrUpdateConfig for WebContent
      Mar 23, 2015 10:29:12 AM javaposse.jobdsl.plugin.JenkinsJobManagement updateExistingItem
      WARNING: Error writing updated item to file.
      java.io.IOException: Failed to persist config.xml
      	at hudson.model.AbstractItem.updateByXml(AbstractItem.java:646)
      	at javaposse.jobdsl.plugin.JenkinsJobManagement.updateExistingItem(JenkinsJobManagement.java:378)
      	at javaposse.jobdsl.plugin.JenkinsJobManagement.createOrUpdateConfig(JenkinsJobManagement.java:123)
      	at javaposse.jobdsl.dsl.DslScriptLoader.extractGeneratedJobs(DslScriptLoader.java:120)
      	at javaposse.jobdsl.dsl.DslScriptLoader.runDslEngine(DslScriptLoader.java:97)
      	at javaposse.jobdsl.plugin.ExecuteDslScripts.perform(ExecuteDslScripts.java:203)
      	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
      	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761)
      	at hudson.model.Build$BuildExecution.build(Build.java:203)
      	at hudson.model.Build$BuildExecution.doRun(Build.java:160)
      	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536)
      	at hudson.model.Run.execute(Run.java:1751)
      	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      	at hudson.model.ResourceController.execute(ResourceController.java:89)
      	at hudson.model.Executor.run(Executor.java:240)
      Caused by: org.xml.sax.SAXException: SAX2 driver class org.apache.xerces.parsers.SAXParser not found
      java.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser
      	at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:230)
      	at org.xml.sax.helpers.XMLReaderFactory.createXMLReader(XMLReaderFactory.java:191)
      	at jenkins.util.xml.XMLUtils.safeTransform(XMLUtils.java:48)
      	at hudson.model.AbstractItem.updateByXml(AbstractItem.java:641)
      	... 14 more
      Caused by: java.lang.ClassNotFoundException: org.apache.xerces.parsers.SAXParser
      	at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
      	at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
      	at java.security.AccessController.doPrivileged(Native Method)
      	at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
      	at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
      	at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
      	at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:430)
      	at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:383)
      	at org.xml.sax.helpers.NewInstance.newInstance(NewInstance.java:82)
      	at org.xml.sax.helpers.XMLReaderFactory.loadClass(XMLReaderFactory.java:228)
      	... 17 more
      

        Attachments

        1. support_2016-07-01_13.06.55.zip
          1.06 MB
        2. support_KO.zip
          18 kB
        3. support_OK.zip
          18 kB
        4. support.zip
          29 kB

          Issue Links

            Activity

            Hide
            tiller Michael Longo added a comment -

            Ulli Hafner : stupid question, are analysis-core and warnings plugins visible in the plugin list in Jenkins UI? Because I don't have any of these plugins in my jenkins and I still had the issue. So is it related?

            Show
            tiller Michael Longo added a comment - Ulli Hafner : stupid question, are analysis-core and warnings plugins visible in the plugin list in Jenkins UI? Because I don't have any of these plugins in my jenkins and I still had the issue. So is it related?
            Hide
            drulli Ulli Hafner added a comment -

            Yes these plugins are visible (static analysis utilities plugin and warning plugin). It is still not clear which plugins are actually causing the bug, so yes you can be affected even if you do not have these plugins installed.

            Show
            drulli Ulli Hafner added a comment - Yes these plugins are visible (static analysis utilities plugin and warning plugin). It is still not clear which plugins are actually causing the bug, so yes you can be affected even if you do not have these plugins installed.
            Hide
            drulli Ulli Hafner added a comment -

            And an additional note: the problem is not that the sax parser is a dependency of a plugin, somehow some plugin sets the property and should not do it.

            Show
            drulli Ulli Hafner added a comment - And an additional note: the problem is not that the sax parser is a dependency of a plugin, somehow some plugin sets the property and should not do it.
            Hide
            drulli Ulli Hafner added a comment -

            In the new beta of the warnings-ng plugin a warning is now logged if your system has a non empty sax parser property. Can you please check the log output on your system if there is such a warning?

            Show
            drulli Ulli Hafner added a comment - In the new beta of the warnings-ng plugin a warning is now logged if your system has a non empty sax parser property. Can you please check the log output on your system if there is such a warning?
            Hide
            bish Bukama Marenellin added a comment -

            Where do I have do search for this warning? I don't see anyone in the build console log output. Does this means the property is correct?

            Struggeling on the problem since our jenkins was updated by the admins to 2.138

             

            Do I understand the other commenty correctly that removing all of the analysis plugins and only use warning-ng should fix that?

            Show
            bish Bukama Marenellin added a comment - Where do I have do search for this warning? I don't see anyone in the build console log output. Does this means the property is correct? Struggeling on the problem since our jenkins was updated by the admins to 2.138   Do I understand the other commenty correctly that removing all of the analysis plugins and only use warning-ng should fix that?

              People

              • Assignee:
                Unassigned
                Reporter:
                andrewk Andrew Kujtan
              • Votes:
                9 Vote for this issue
                Watchers:
                23 Start watching this issue

                Dates

                • Created:
                  Updated: