-
Bug
-
Resolution: Done
-
Blocker
-
7.1.6.CR1
-
-
-
-
-
-
Workaround Exists
-
It seems that JBEAP-15434 introduced an issue in jbossws-common's DOMUtils, causing following exception:
14:35:17,906 ERROR [stderr] (default task-1) javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found 14:35:17,907 ERROR [stderr] (default task-1) at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:200) 14:35:17,907 ERROR [stderr] (default task-1) at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:152) 14:35:17,907 ERROR [stderr] (default task-1) at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:163) 14:35:17,908 ERROR [stderr] (default task-1) at org.jboss.ws.common.DOMUtils$1.initialValue(DOMUtils.java:113) 14:35:17,908 ERROR [stderr] (default task-1) at org.jboss.ws.common.DOMUtils$1.initialValue(DOMUtils.java:100) 14:35:17,908 ERROR [stderr] (default task-1) at java.lang.ThreadLocal.setInitialValue(ThreadLocal.java:180) 14:35:17,908 ERROR [stderr] (default task-1) at java.lang.ThreadLocal.get(ThreadLocal.java:170) 14:35:17,908 ERROR [stderr] (default task-1) at org.jboss.ws.common.DOMUtils.getDocumentBuilder(DOMUtils.java:200) 14:35:17,908 ERROR [stderr] (default task-1) at org.jboss.ws.common.DOMUtils.parse(DOMUtils.java:250) 14:35:17,909 ERROR [stderr] (default task-1) at org.jboss.ws.common.DOMUtils.parse(DOMUtils.java:211)
This is a regression agains EAP 7.1.5.
Upstream was already fixed in JBWS-4114, but we need to backport the fix for EAP 7.1.z.
The issue goes away when -Dorg.jboss.ws.alwaysResolveDocumentBuilderFactory=true is used.
- clones
-
-
- Closed
-
- is caused by
-
-
- Closed
-
- is incorporated by
-
JBEAP-16142 [GSS](7.1.z) Upgrade JBossWS Common from 3.1.6.Final to 3.1.7.Final
-
- Closed
-
