Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Won't Fix
-
1.605 Win64 Job DSL 1.30
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
Issue Links
- is blocking
-
-
- Resolved
-
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
- is related to
-
-
- Resolved
-
Activity
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.
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?
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?
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? The plugin is deprecated and not maintained anymore. Please upgrade to the warnings-ng plugin.
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.