Hi Bertram
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.
Hmm.. but I guess that a problem between Apache -> Tomcat, and not
related to the Synapse -> Apache interaction, but yes.. it is
interesting..
Ok, I can confirm this. After convincing my network admin, I could connect
directly to the tomcat instance, and that solved the problem immediately.
We haven't looked at the network packages yet, but it really seems to be a
problem in the apache http<->tomcat communication.
Cool :-) .. let us know once you find out the root cause, as it will be
helpful to other users too
asankha
--
Asankha C. Perera
WSO2 - http://wso2.org
http://esbmagic.blogspot.com
