The upgrade worked - I can now submit my file successfully.
Brenda Coulson wrote: > > Thanks for the quick reply. I am in the process of upgrading to CXF 2.2.6 > and will let you know if that corrects the problem. I did turn off logging > but that did not change the behavior. > > > dkulp wrote: >> >> >> Definitely try with CXF 2.2.6 if you are not already using 2.2.6. We've >> made >> a lot of improvements in attachment handling in the last couple versions >> to >> make them faster and more memory efficient. >> >> If it's still an issue, is there any way a small test case could be >> provided. >> I know we have tests that test echoing of attachments of around that size >> so >> it should be OK. >> >> Dan >> >> >> On Tue January 26 2010 4:11:06 pm Brenda Coulson wrote: >>> I have scoured the discussion forums, tried multiple attempts to >>> understand >>> why this is happening all to no avail. I have a CXF Client that invokes >>> a >>> method on my web service that should have a SOAP attachment. The >>> attachment >>> can either be an XML file or a ZIP file. The WSDL defines the attachment >>> as >>> having type application/octet-stream. >>> >>> Everything works fine for zip, gzip or text/xml files up to a certain >>> size. >>> When I try to submit a xml file that is 4.5 MB in size, the file is >>> actually truncated before it is sent to the server. So when the server >>> receives the file, it complains, rightly so, of a "Premature End Of >>> File" >>> error. >>> >>> Does anyone have any suggestions on what could be causing this >>> truncation? >>> >>> Regards >>> Brenda >>> >> >> -- >> Daniel Kulp >> [email protected] >> http://www.dankulp.com/blog >> >> > > -- View this message in context: http://old.nabble.com/Large-SOAP-Attachment-getting-truncated-using-JAX-WS-tp27329816p27344645.html Sent from the cxf-user mailing list archive at Nabble.com.
