I did that; and the response is valid XML but the doctype is expected to be something like
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML/2.0//EN"> Instead of <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> PS: notice a forward slash before 2.0 in the correct one. The problem is that it will take very long time to go thru build/test cycle of that product, and if I can change that behavior in Synapse configuration that would help. Regards, Abid -----Original Message----- From: Paul Fremantle [mailto:[email protected]] Sent: Tuesday, May 15, 2012 6:16 AM To: [email protected] Subject: Re: how can I avoid this exception Abid A good approach is to put TCPMON in the middle to look at exactly what the server is responding to the Synapse engine. Paul On Tue, May 15, 2012 at 1:19 AM, Abid Khan <[email protected]> wrote: > Hello all, > > I am getting following fault from synapse, It looks like the > application is sending back an protocol version that synapse cannot > accept, is there any way I can avoid this issue? > > > <soapenv:Fault > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";><faultcode > xmlns:tns="http://www.w3.org/2003/05/soap-envelope";>tns:Receiver</faultcode><faultstring>org.apache.axis2.AxisFault: > org.apache.http.ProtocolException: Not a valid protocol version: > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML > 2.0//EN"></faultstring></soapenv:Fault > > > Regards, > Abid Khan > -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [email protected] "Oxygenating the Web Service Platform", www.wso2.com
