[SWS-300] SAAJ0539: Unable to get header stream in saveChanges Created: 28/Feb/08  Updated: 05/May/08  Resolved: 27/Apr/08

Status: Closed
Project: Spring Web Services
Component/s: Core
Affects Version/s: None
Fix Version/s: 1.5.1

Type: Bug Priority: Major
Reporter: JIGNESH Assignee: Arjen Poutsma
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Sun SPARC, Oracle AS, Web application (WAR) on OC4J Component


Attachments: Text File log.txt    

 Description   

at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:824)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:224)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:133)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:534)
Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to get header stream in saveChanges:
at com.sun.xml.messaging.saaj.soap.MessageImpl.saveChanges(MessageImpl.java:541)
at com.sun.xml.messaging.saaj.soap.MessageImpl.writeTo(MessageImpl.java:591)
at labware.connector.j2c.LIMSSOAPWrapper.createSOAPFromCallDetails(LIMSSOAPWrapper.java:391)
... 28 more
Caused by: java.io.IOException
at com.sun.xml.messaging.saaj.soap.impl.EnvelopeImpl.output(EnvelopeImpl.java:240)
at com.sun.xml.messaging.saaj.soap.SOAPPartImpl.getContentAsStream(SOAPPartImpl.java:202)
at com.sun.xml.messaging.saaj.soap.MessageImpl.getHeaderBytes(MessageImpl.java:461)
at com.sun.xml.messaging.saaj.soap.MessageImpl.saveChanges(MessageImpl.java:538)
... 30 more



 Comments   
Comment by JIGNESH [ 28/Feb/08 ]

We have deployed a web application on OC4J >> Oracle Application Server. This application runs fine with Tomcat. When we deployed on OAS, it is raising above exception. Please give solution. Thanks

Comment by Arjen Poutsma [ 17/Apr/08 ]

Which version of Spring-WS is this?

Comment by Arjen Poutsma [ 27/Apr/08 ]

I cannot reproduce this. Make sure you have Xerces 2.8.1 and Xalan 2.7.0 on the classpath, and that they override the OC4J versions. That always does the trick for me.

Comment by Arjen Poutsma [ 27/Apr/08 ]

I cannot reproduce this. Make sure you have Xerces 2.8.1 and Xalan 2.7.0 on the classpath, and that they override the OC4J versions. That always does the trick for me.

Comment by Arjen Poutsma [ 05/May/08 ]

Closing issues for 1.5.1

Generated at Fri Dec 15 15:49:48 UTC 2017 using JIRA 6.4.14#64029-sha1:ae256fe0fbb912241490ff1cecfb323ea0905ca5.