Forum Discussion

jsauvard's avatar
jsauvard
New Contributor
12 years ago

Would SoapUI close HTTP connection on 500 error?

Hi,

I'm struggling since a couple of days on a problem I'm having with multiple client BUT SoapUI.

When I send an incorrect request to the target webservice, every client I've been testing so far is giving back a time out response. For instance, in a simple browser, if I set the URL to the webservice address, the browser only prints back the XML response after the default 3-minute timeout.

Since the response does not set Content-Length, I presume the server does not close the HTTP connection and this leads to the timeout.

However, SoapUI perfectly reads the output of the server and does not timeout. This is the very single client I've been using that behaves this way and this prevents me from proving 100% that this is the server that does not close the connection.

Has anyone experienced such an identical behaviour or can someone from SmartBear confirm me that SoapUI actually assumes the HTTP connection is finished after it receives soap-end:Envelope close tag or something like that?

Thanks in advance for help.

3 Replies

  • jsauvard's avatar
    jsauvard
    New Contributor
    12 years ago
    Hi,

    thanks for feedback, however, this is not exactly what I've been looking for.

    The problem (I assume) I have is with a server that does not close properly the HTTP connection.
    If I read properly the specification for HTTP: http://www.w3.org/Protocols/rfc2616/rfc ... tml#sec4.4

    I receive a 500 response without Content-Length, thus the server should be closing the connection for the message to be read.
    All clients (but SOAP UI) I have been using end up with a timeout.
    My browser displays something only after the default browser timeout of 3 minutes.
    SOAP UI displays the server response without any time out.

    Would you know of any SOAP UI feature as a client that would lead to such a behaviour?
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    12 years ago
    I see. In SoapUI Pro, again you can control the timeout for your requests (File > Preferences > HTTP Settings tab > Socket Timeout (ms))
    By default, as in your instance I assume, this timeout is not set and SoapUI waits indefinitely for a response. So somewhere in your client code I assume the timeout is set and reached.

    Thanks,
    Michael Giller
    SmartBear Software