Uploaded image for project: 'Axis2'
  1. Axis2
  2. AXIS2-4996

Exclude content-length header while chunked is enabled

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 1.6.0
    • None
    • transports

    Description

      I am running Axis2 on Tomcat 7, and get some exception message saying :
      --->
      java.util.concurrent.ExecutionException: javax.xml.ws.soap.SOAPFaultException: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character 'f' (code 102) in prolog; expected '<'
      at [row,col

      {unknown-source}]: [1,1]
      at org.apache.axis2.jaxws.client.async.AsyncResponse.onError(AsyncResponse.java:141)
      at org.apache.axis2.jaxws.client.async.AsyncResponse.onError(AsyncResponse.java:95)
      at org.apache.axis2.jaxws.client.async.CallbackFutureTask.call(CallbackFuture.java:326)
      at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
      at java.util.concurrent.FutureTask.run(FutureTask.java:138)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      at java.lang.Thread.run(Thread.java:619)
      Caused by: javax.xml.ws.soap.SOAPFaultException: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character 'f' (code 102) in prolog; expected '<'
      at [row,col {unknown-source}

      ]: [1,1]
      at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.createSystemException(MethodMarshallerUtils.java:1326)
      at org.apache.axis2.jaxws.client.dispatch.BaseDispatch.getFaultResponse(BaseDispatch.java:839)
      at org.apache.axis2.jaxws.client.dispatch.XMLDispatchAsyncListener.getFaultResponse(XMLDispatchAsyncListener.java:70)
      at org.apache.axis2.jaxws.client.async.AsyncResponse.processFaultResponse(AsyncResponse.java:431)
      at org.apache.axis2.jaxws.client.async.AsyncResponse.onError(AsyncResponse.java:129)
      ... 7 more
      <---
      From the sec 4.4.3 of http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html, if the server found both Transfer-Encoding header field and a Content-Length header field, the latter MUST be ignored. It might be a bug in Tomcat, but if Axis2 could remove the content-length header in advance, that would be more compatibility and efficiency.

      Attachments

        1. Axis2-4996.patch
          2 kB
          Haihong Xu

        Activity

          People

            hiranya Hiranya Kasub Jayathilaka
            xuhaihong Haihong Xu
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated: