|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
The cause of this error is probably the different packaging of Xerces in Oracle and IBM JDK.
Oracle JDK packages the class in question as com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactory, while in the IBM J9 JDK it is packaged as org.apache.xerces.jaxp.DocumentBuilderFactoryImpl.
It looks like the violations plugin on the slave looks for the DocumentBuilderFactoryImpl configured on the master (which is not there) - probably because the DocumentBuilderFactory is serialized on the master and sent to the client for execution (the default impl class is hardcoded in DocumentBuilderFactory).
This means this is a general problem (and not IBM J9 specific) - any master with a alternate DocumentBuilderFactoryImpl configured (as compared to Oracle JDK) will cause this error.
The DocumentBuilderFactory javadoc http://docs.oracle.com/javase/6/docs/api/javax/xml/parsers/DocumentBuilderFactory.html states how the impl class is resolved - does setting the system property javax.xml.parsers.DocumentBuilderFactory, e.g.
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactory
on the slave help?