Well, I spoke too soon. Turning off chunking solved problem with the previous soap request, but it raised it's ugly head in another call.
buzzterrier wrote: > > btw, turning off chunking worked. Thx for the advice. > > > > buzzterrier wrote: >> >> I have the wireshark dump, and a sample of the soap request that fails. >> In the soap request the following line is the culprit: >> <ns9:description>PM361001-DJ01</ns9:description> >> >> if I remove the dash, it does not fail. >> >> I also have another request that fails consistently if you are >> intersested. >> >> http://www.nabble.com/file/p21981477/trailingcontent.zip >> trailingcontent.zip >> >> dkulp wrote: >>> >>> >>> >>> Two thoughts: >>> >>> 1) Any chance you could use something like wireshark to get the raw >>> byte >>> streams? We had one other report a month or two ago about extra bytes >>> at the >>> end of the message, but no-one could ever reproduce it and the thought >>> was >>> that the proxy server in the middle or some other wrapper was adding it. >>> >>> 2) You could also try turning off http chunking. Some older servers >>> don't >>> properly support it. Maybe the "0" at the end to mark the end of the >>> chunk >>> is pushing through to the parser or something. >>> >>> Dan >>> >>> >>> >>> On Wed February 11 2009 7:19:04 pm buzzterrier wrote: >>>> I am getting the following error when sending a soap request to a >>>> remote >>>> service and I am not quite sure who is throwing it. I found that this >>>> is >>>> sometimes thrown when some elements had text containing unescaped >>>> extended >>>> characters. But I have some posts that are failing and I cannot see >>>> anything wrong with the package. I am kind of new to SOAP so I am not >>>> sure >>>> if CXF is causing this error, or if the server that is consuming the >>>> SOAP >>>> message is. >>>> >>>> Here is an fault message: >>>> >>>> <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope >>>> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; >>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; >>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";><soapenv:Body><soapen >>>>v:Fault><faultcode>soapenv:Server.userException</faultcode><faultstring>org. >>>>xml.sax.SAXParseException: Content is not allowed in trailing >>>> section.</faultstring><detail><ns1:hostname >>>> xmlns:ns1="http://xml.apache.org/axis/";>sb-partners-java002.svale.netledger >>>>.com</ns1:hostname></detail></soapenv:Fault></soapenv:Body></soapenv:Envelop >>>>e> >>>> >>>> Should I go harp on the service provider? Does anyone have any idea >>>> what >>>> else might cause that message? >>>> >>>> ----- >>>> Buzzterrier >>>> >>>> http://buzzterrier.blogspot.com/ View my blog: Ordinary Average >>>> Developer... >>> >>> -- >>> Daniel Kulp >>> dk...@apache.org >>> http://www.dankulp.com/blog >>> >>> >> >> > > ----- Buzzterrier http://buzzterrier.blogspot.com/ View my blog: Ordinary Average Developer... -- View this message in context: http://www.nabble.com/SAXParseException---who%27s-to-blame--tp21967512p21986861.html Sent from the cxf-user mailing list archive at Nabble.com.
