2 Replies Latest reply on Apr 10, 2008 9:54 AM by gbuys

    Transfer-encoding chunked

    gbuys

      Hi All,

      I'm having an issue calling a webservice on MS IIS from JBoss 4.2.2 with Apache CXF 2.0.4 client deployed in a Spring application.

      The deployed service doesn't seem to support client calls from JBoss with Transfer-encoding chunked in the request header. Sometimes the service system gives a response but most of the time it hangs or returns an error message. I've deployed exactly the same client code (generated with soapUI using CXF 2.0.4.-incubator) in a stand alone program in Eclipse. This program sends requests to the service with a content-length specified in the request header. This works perfectly well, the IIS server quickly responds and remains stable.

      So it appears to me that JBoss is actually responsible for putting the 'Transfer-encoding chunked' in the header. How can I reconfigure my JBoss to send requests with fixed content length. As a matter of fact, I think I should configure that only the web service requests have content-length specified. All other requests/responses should remain chunked.

      Or do I have to configure CXF or change my service client code to force the requests having a content-length header? I did some experiments with a cxf-servlet.xml in my WEB-INF without succes (ip address replaced with x's):

      <beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xmlns:http-conf="http://cxf.apache.org/transports/http/configuration"
       xsi:schemaLocation="http://cxf.apache.org/transports/http/configuration
       http://cxf.apache.org/schemas/configuration/http-conf.xsd
       http://www.springframework.org/schema/beans
       http://www.springframework.org/schema/beans/spring-beans.xsd">
      
       <http-conf:conduit
       name="{http://xx.xx.xx.xx/Webservice_Server/}Webservice_Server.http-conduit">
       <http-conf:client AllowChunking="false"/>
       </http-conf:conduit>
      </beans>
      


      Any help is greatly appreciated!
      (Of course, the guys on the web service side should find out why their IIS becomes unstable, but i'd like to find out what i can change on the client side as well...)