We sometimes have issues where individual XML POSTs fail when using jk2 w/ Apache 2.0 and Tomcat 5.0.16. We have re-run the posts using just tomcat on port 80, and the post are then successful. We think the problem is within the AJP13 conversation at this time...
The error we receive when there is a failure is as follows (first 2 lines are slightly edited due to AJP being binary in nature...): Internal Server Error Content-Type text/xml;charset=utf-8 <?xml version="1.0" encoding="UTF-8"?> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmln s:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSc hema-instance"> <soapenv:Body> <soapenv:Fault> <faultcode>soapenv:Server.userException</faultcode> <faultstring>org.xml.sax.SAXParseException: The element type "soap:Envel ope" must be terminated by the matching end-tag "</soap:Envelope> ;".</faultstring> <detail/> </soapenv:Fault> </soapenv:Body> </soapenv:Envelope> When doing an AJP13 network trace on the post, the only interesting thing that I notice is that the trailing </soap:Envelope> is split up by a GET BODY CHUNK request from the server. So it looks like this: GET BODY CHUNK (Server) Send Data....</soap:Envelop GET BODY CHUNK (Server) Send e> ERROR (server) (see above) Since the actual XML content isn't part of the protocol, I assume that this shouldn't be a problem. It's the only "guess" I can come up with regarding why a small number of posts fail when using JK2. Any thoughts are appreciated... perhaps I should move away from JK2? Is it (or the tomcat AJP connector) known to have problems such as this? thnx -Blaine --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
