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 ...
Forum Discussion
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.