Forum Discussion

PMI_Mortgage_In_1's avatar
PMI_Mortgage_In_1
Occasional Contributor
13 years ago

Issues with WS call when adding HTTP parm Transfer-Encoding

Issues with WebService call when adding HTTP parameter Transfer-Encoding=true

We use WebSphere Enterprise Service Bus (WESB) for developing and publishing the web services. We're able to test these web services using SoapUI 4.0. But on adding HTTP parameter Transfer-Encoding=true, the web service started to return following error message -

<soapenv:Fault><faultcode></faultcode><faultstring>Illegal chunk length digit: 60</faultstring><detail></detail></soapenv:Fault>

We opened a bug with IBM for this as a WESB defect. After analysing the issue with TCP dump and other application server logging, IBM came back and told that the client application is not sending the correct chunked data format. Please work with the application code, which is creating and sending the incorrect chunked data. Following reason was provided by IBM.

We can see the request coming in
? [8/18/11 13:47:31:812] 0000006a HttpRequestMe [setRequestURL: set URI to /mywebservice/export]
..
> [8/18/11 13:47:31:828] 0000006a WASAxis2Servl.doPost() [Entry]
..
? [8/18/11 13:47:31:857] 0000006a HttpServiceCo [Reading body, chunked]
..
? [8/18/11 13:47:31:858] 0000006a HttpServiceCo [Client sent a bad chunk: 60]

From the IP trace -
0000 00 1a 64 96 e6 a5 00 30 f2 ea 5b fc 08 00 45 00 ..d....0..[...E.
0010 00 56 92 20 40 00 7e 06 58 1a 0a 03 e9 4b 0a 03 .V. @.~.X....K..
0020 15 16 0b ca 25 8f f5 3f 98 df 34 74 d7 89 50 18 ....%..?..4t..P.
0030 fc 00 45 d4 00 00 4d 69 44 61 74 61 3e 0a 20 20 ..E...Mi Data>.
0040 20 3c 2f 73 6f 61 70 65 6e 76 3a 42 6f 64 79 3e </soapenv:Body>
0050 0a 3c 2f 73 6f 61 70 65 6e 76 3a 45 6e 76 65 6c .</soapenv:Envel
0060 6f 70 65 3e ope>

The chunk should end with OD OA OD OA value which it is missing.


This issue is very critical to us for our testing. Can you please look into this and do the needful.

3 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    Hi,

    hmm.. do you have a value set for the "Chunking Threshold" in the global HTTP Settings?

    Can you show the request as it is logged in the soapUI http log (at the bottom of the main window) ?

    thanks in advance!

    /Ole
    SmartBear Stockholm
  • PMI_Mortgage_In_1's avatar
    PMI_Mortgage_In_1
    Occasional Contributor
    Thank you for your reply. One thing I had not set was "Chunking Threshold" in the global HTTP Settings. As soon as I set that I started to get the responses. So I think this was an configuration issue and not a defect. I tried with few values for "Chunking Threshold" and both of these worked fine. Thanks for your help.