My comment basically means that server is not really stable. Sometime it responds correctly and sometime the response is not valid. In last case I don’t have much detail about the error itself. I can check that some encrypted data was actually received from the server. In my attempts I’ve checked that some data was actually received and sometimes system cannot decrypt it. So in this case it is not the connection close story.
About the connection close story itself: It’s not a simple case. I want to explain the connection close thing for everybody who was not a part of this discussion. Sometimes server can decide to close the connection for some reason. The reason itself is a most interesting part of this problem. For last request in the connection it’s ok and sometime it’s really expected behavior (case 1). For some middle request it’s an error since the following requests in closed connection will not be simulated. Server under the big load pressure can close some of the connections to protect itself (case 2). Sometime server can receive unexpected authorization results such as incorrect credentials or unexpected response sequence. In most cases it will close the connection (case 3). ASP.NET server can receive broken event or session data. The server will responds with 500 and close the connection (case 4).
The list of cases is not full. It cannot be full.
As Alexei already noted, WebLoadUI will detect errors in case a server will close the connection and will not simulate some recorded requests. This is the indication of the error. The explanation may be found by connection close note that posted in the log if WebLoadUI can detect a disconnection. Sometime it is not possible and request simulation will be stopped due to timeout. I’ll post timeout error in the log in this case. For the last case 500 is the indicator.
The list of possible indicators and resolution is not full as well. But I hope it can help.
