Hi asankha, > First of all, you need to subscribe to this mailing list (see > http://synapse.apache.org/mail-lists.html) to receive our replies to > your queries.. for now, I have explicitly copied this response to you..
Until know I've been using the RSS feed to read the list. Nonetheless, answering is much simpler with a subscrition. :) > >> When I invoke a request on that service, it forwards that request >> (unmodified), but the receiving server runs into an error > What exactly is the error? and whats the receiving system - is it .Net ? > Can it understand HTTP 1.1 (chunked encoding) or is it HTTP 1.0 only ? On the receiving system, the request hits an Apache (don't know which version of it), which forwards it to a tomcat 4 installation using the ajp connector. So it supports http 1.1/chunked encoding. Maybe it's interesting to know that the service consumer application only speaks http 1.0. >> Wireshark gave me a hint on this: >> >> POST http://ws001/soap/v1/WS_Customer_Control HTTP/1.1 >> Host: localhost:8280 >> SOAPAction: "" >> Accept: application/soap+xml, application/dime, multipart/related, >> text/* >> Pragma: no-cache >> Cache-Control: no-cache >> Content-Type: text/xml; charset=utf-8 >> Transfer-Encoding: chunked >> Connection: Keep-Alive >> User-Agent: Synapse-HttpComponents-NIO >> >> <?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";>..[original >> content]..]</soapenv:Envelope> >> > I spot an error here.. the "Host: localhost:8280" is wrong.. is the host > "ws001" the same machine?.. anyway the port 8280 is wrong, .. No, it's not. The service consumer and the synapse installation are both running on my local workspace machine. The service provider runs on ws001. So the host header seems to be exactly what synapse receives from the service consumer. > [...] > The "POST http://xxx HTTP/1.1" format is used when messages are sent > through proxies, and this should not have any adverse effects on your > Apache.. or is it the real backend service which complains? anyway let > me know the environment that does not understand this form, and I will > fix this issue ASAP The error message seems to originate from the tomcat 4, on which the service is installed. It seems to have troubles figuring out the webapp that should handle the request. Unfortunately the target system runs an third party application, so we can't just switch over to a new tomcat version. Bertram -- Bertram Fey Portale und Web-Technologie ENTEGA Service GmbH Landwehrstraße 55 64293 Darmstadt Telefon: +49 (0)6151 970-2045 Telefax: +49 (0)6151 970-2289 E-Mail: [EMAIL PROTECTED] Internet: http://www.entega-service.de ENTEGA Service - ein Unternehmen der HEAG Südhessischen Energie AG (HSE) und der Stadtwerke Mainz AG .......................................................................................... ENTEGA Service GmbH Geschäftsführung: Dipl.-Ing. Johannes Brüssermann (Sprecher) Dipl.-Kfm. Volker Abert Sitz der Gesellschaft: Mainz Registergericht: Amtsgericht Mainz HRB 3950
