Forum Discussion

nicholasglen's avatar
nicholasglen
Contributor
13 years ago

Controlling Closing of Connection

Hello,
We have a soap application that issues faults. The soap standard is that it will set the http return code of 500 if it gets a fault, and on a normal response it will set 200. The problem we are having is that when a soap fault is thrown it drops the connection. When we get repeated faults this causes connection refused errors at it is not reusing connections. From what I can tell loadUI drops the connection unless when it receives a 500. Is there a way to control that as soap faults can be a result of just normal business process.
Thanks,
Glen

3 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    13 years ago
    Hi,
    Good question. This is a interesting issue. There could be something that can be done inside SoapUI.

    Have you tried running the test in SoapUI and checked if it also drops the connection when it receives a 500 code?

    Regards,
    Max
    LoadUI developer
  • nicholasglen's avatar
    nicholasglen
    Contributor
    13 years ago
    Yes, in soapUI it drops the connection. However, in a soap fault scenario this should not happen as a fault can be a business condition or a system exception of some sort. We opened up an issue with IBM initially as we thought WebSphere had trouble handling them, but when we built our own java client we do not get the same behavior. What it results in under load(only 5 tps) is a connection refused issue, probably because of always recreating connections. We would expect the connection to stay active. In soapUI you can see the connection dropped in the http log.
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    13 years ago
    Hi Nicholas,

    Have you tried enabling the TestCase option "Maintain HTTP session" (right-click on the test-case and click on the "Options" button)?

    Renato
    SmartBear Software