SAAJ0511: Unable to create envelope from given source [SWS-175]

[gregturn]

Ralph Pöllath opened SWS-175 and commented

I just encountered SAAJ0511 on Tomcat 5.5.23 with Sun JVM 1.6.0_01-b06:

24.08.2007 16:42:51 com.sun.xml.internal.messaging.saaj.soap.EnvelopeF actory createEnvelope
ERROR: SAAJ0511: Unable to create envelope from given source
24.08.2007 16:42:51 com.sun.xml.internal.messaging.saaj.soap.MessageIm pl saveChanges
ERROR: SAAJ0539: Unable to get header stream in saveChanges
24.08.2007 16:42:51 com.sun.xml.internal.messaging.saaj.soap.MessageIm pl saveChanges
ERROR: SAAJ0540: Error during saving a multipart message

Servlet.service() for servlet xyz threw exception java.io.IOException
at com.sun.xml.internal.messaging.saaj.soap.impl.Enve lopeImpl.output(EnvelopeImpl.java:298)
at com.sun.xml.internal.messaging.saaj.soap.impl.Enve lopeImpl.output(EnvelopeImpl.java:309)
at com.sun.xml.internal.messaging.saaj.soap.SOAPPartI mpl.getContentAsStream(SOAPPartImpl.java:305)
at com.sun.xml.internal.messaging.saaj.soap.MessageIm pl.getHeaderBytes(MessageImpl.java:947)
at com.sun.xml.internal.messaging.saaj.soap.MessageIm pl.saveChanges(MessageImpl.java:1098)
at org.springframework.ws.soap.saaj.Saaj13Implementat ion.writeTo(Saaj13Implementation.java:259)
at org.springframework.ws.soap.saaj.SaajSoapMessage.w riteTo(SaajSoapMessage.java:105)
at org.springframework.ws.transport.AbstractWebServic eConnection.send(AbstractWebServiceConnection.java :36)
at org.springframework.ws.transport.support.WebServic eMessageReceiverObjectSupport.handleConnection(Web ServiceMessageReceiverObjectSupport.java:96)
at org.springframework.ws.transport.http.WebServiceMe ssageReceiverHandlerAdapter.handle(WebServiceMessa geReceiverHandlerAdapter.java:57)
at org.springframework.ws.transport.http.MessageDispa tcherServlet.doService(MessageDispatcherServlet.ja va:158)
at org.springframework.web.servlet.FrameworkServlet.p rocessRequest(FrameworkServlet.java:475)
at org.springframework.web.servlet.FrameworkServlet.d oPost(FrameworkServlet.java:440)

My app's WEB-INF/lib/ contains xalan-2.7.0.jar and xercesImpl-2.8.1.jar, and I can't find potentially conflicting jars elsewhere in the tomcat installation.

---

Affects: 1.0

Attachments:

• echo-client-webapp.tgz (8.50 kB)
• jaxp-debug-log-sws-175.txt (18.88 kB)
• jaxp-debug-log-sws-175-java5.txt (18.78 kB)
• stacktrace-sws-175.txt (19.26 kB)

[gregturn]

Ralph Pöllath commented

Attaching a stacktrace. The root cause seems to be:

java.io.IOException: org.apache.xml.serializer.ToXMLSAXHandler cannot be cast to org.apache.xml.serializer.SerializationHandler
at com.sun.xml.internal.messaging.saaj.soap.impl.EnvelopeImpl.output(EnvelopeImpl.java:298)

I've taken a closer look at all the jars in my tomcat installation. ToXMLSAXHandler and SerializationHandler are both contained only in WEB-INF/lib/xalan-2.7.0.jar and EnvelopeImpl is only found in WEB-INF/lib/saaj-impl-1.3.jar.

Please let me know if I can further help to sort this out, since I need to come up with a solution or workaround ASAP.

[gregturn]

Ralph Pöllath commented

Attaching JAXP debug log messages, created using -Djaxp.debug=1 .

I also confirmed that the error does not occur with Sun JVM 1.5.0_09-b03 (same app, same tomcat install).

[gregturn]

Ralph Pöllath commented

Attaching JAXP debug log messages produced by java5.

[gregturn]

Arjen Poutsma commented

Indeed. I couldn't reproduce this using tomcat 5.5.23 and JDK 1.5.0_07-87 (on OS X). Will investigate JDK 1.6.

[gregturn]

Arjen Poutsma commented

Unfortunately, I cannot reproduce this using JDK 1.6 either (1.6.0_02-b06). I used the echo sample to test it.

I suspect it has something to do with different version of Xerces and/or Xalan installed. With a clean install, it works for me.

[gregturn]

Ralph Pöllath commented

Attaching a webapp client for the sample echo server that reproduces the problem (at least here :)

It's a webapp that contains the EchoClient found in samples/echo/clientspring-ws. It sends a message to the echo server found in samples/echo/src/. Works with Java 5, but not with Java 6.

It's a standalone Maven2-based app which can be built using mvn package. See the included README.txt for further details.

If you want me to send it including all dependencies, just let me know.

[gregturn]

Ralph Pöllath commented

Haven't made any progress on this so far. The fact that Java 6 contains saaj, and re-packaged versions of xalan and xerces doesn't help at all.

The IOException mentioned above is thrown by EnvelopeImpl in either output(OutputStream out) or output(OutputStream out, boolean isFastInfoset). Both methods catch Exception, and throw a new IOException, thereby re-using the cause's message, but swallowing the stacktrace. Oh well.

"org.apache.xml.serializer.ToXMLSAXHandler cannot be cast to org.apache.xml.serializer.SerializationHandler" leaves me puzzled. ToXMLSAXHandler extends ToSAXHandler, which extends SerializerBase, which implements SerializationHandler. Am I looking at the wrong sources?!

[gregturn]

Ralph Pöllath commented

Oops, looks like there is no Wiki Style Renderer for comments.

[gregturn]

Arjen Poutsma commented

I can actually reproduce this using the client web app you attached. Will investigate further...

[gregturn]

Arjen Poutsma commented

I was able to fix this by removing the xerces and xalan dependencies from the pom in the echo-client-webapp. Without those, the echo client works perfectly.

I think the problem here is that JDK 1.6 ships with JAXP 1.4, and Xerces 2.8.1 is JAXP 1.3. In the JDK 1.6 jars (rt.jar), there is a com.sun.org.apache package, which contains a SUN-specific version of Xerces and Xalan. This package implements JAXP 1.4. AFAIK, there is no Apache-provided JAXP 1.4 implementation yet.

[gregturn]

Arjen Poutsma commented

Closing 1.0.1 issues.