Forum Discussion

dehringer's avatar
dehringer
New Contributor
16 years ago

Responses Truncated after 200 bytes in Test Steps

I am experiencing a problem where some response messages in Test Cases are being truncated after 200 bytes.  This is happening for both SOAP Fault responses and non-SOAP fault responses.  When I view the response in TcpMon, it appears not contain any odd characters and the content-length HTTP header is accurate.  The same exact responses are handled correctly when they aren't in a Test Case/Step (i.e. adhoc requests under an interface) Has anyone experienced this before or know what could be the problem?

Thanks!
Dave

[hr:jfzxnx3o][/hr:jfzxnx3o]

soapUI versions: 3.0.1 and 3.5
Some of the HTTP Settings:

  • Request compression: checked

  • Response compression: unchecked

  • Close connections after request: unchecked

  • Chunking Threshold: empty

  • Enable Mock HTTP Log: unchecked


The response in TcpMon:
[tt:jfzxnx3o]HTTP/1.1 500 Internal Server Error
Accept: text/xml, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
SOAPAction: ""
Content-Type: text/xml; charset=utf-8
Content-Length: 762
Server: Jetty(6.1.10)

SOAP-ENV:ClientError caused by invalid information provided by clientLIBP02P-GI1LZKFUNKNOWNcvc-complex-type.2.4.d: Invalid content was found starting with element 'Request'. No child element is expected at this point.
[/tt:jfzxnx3o]

Response in the test step response window:
[tt:jfzxnx3o]
SOAP-ENV:ClientError caused by invali[/tt:jfzxnx3o]

soapUI HTTP Log:
[tt:jfzxnx3o]Wed Apr 07 16:56:14 EDT 2010:DEBUG:<< "HTTP/1.1 500 Internal Server Error[\r][\n]"
Wed Apr 07 16:56:14 EDT 2010:DEBUG:<< "HTTP/1.1 500 Internal Server Error[\r][\n]"
Wed Apr 07 16:56:14 EDT 2010:DEBUG:<< "Accept: text/xml, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2[\r][\n]"
Wed Apr 07 16:56:14 EDT 2010:DEBUG:<< "SOAPAction: ""[\r][\n]"
Wed Apr 07 16:56:14 EDT 2010:DEBUG:<< "Content-Type: text/xml; charset=utf-8[\r][\n]"
Wed Apr 07 16:56:14 EDT 2010:DEBUG:<< "Content-Length: 762[\r][\n]"
Wed Apr 07 16:56:14 EDT 2010:DEBUG:<< "Server: Jetty(6.1.10)[\r][\n]"
Wed Apr 07 16:56:14 EDT 2010:DEBUG:<< "[\r][\n]"
Wed Apr 07 16:56:14 EDT 2010:DEBUG:<< "
SOAP-ENV:ClientError caused by invali"
Wed Apr 07 16:56:14 EDT 2010:DEBUG:<< "d information provided by client
LIBP02P-GI1LZKFUNKNOWNcvc-complex-type.2.4.d: Invalid content was found starting with element 'Request'. No child element is expected at this point.
"[/tt:jfzxnx3o]

Test Assertions are failing with errors like:
[tt:jfzxnx3o]line -1: error: Unexpected end of file after faultstring
line 1: Unexpected end of file after faultstring[/tt:jfzxnx3o]

2 Replies

  • Hi!

    hm.. any errors in the error log when this happens? Have you by  chance/mistake set the Max Size property of the request to 200 (in the bottom left table of properties..)?

    regards!

    /Ole
    eviware.com
  • dehringer's avatar
    dehringer
    New Contributor
    That was it!  The Max Size must have been accidentally set for a test case and then that test case was cloned a bunch of times, which is why it worked for some and not others.

    I appreciate the quick response.

    Thanks again,
    Dave