This error has a number of possible causes, though in most instances it is the result of a failure or limitation in one of the components of the System Under Test (SUT), usually under load conditions. Definition of the error: The "HTTP 1011 - unexpected connection close during read" error occurs when an open connection to the server, on which the SilkPerformer replay engine expects to receive more data, is closed before that data is received and without the normal TCP handshake for closing connections gracefully. This handshake should be as follows: i. Server: FIN ii. Client: ACK iii. Client: FIN iv. Server: ACK Thus, for example, the error will occur if the server under test sends a TCP RESET to close the connection unexpectedly. It may also occur if the connection was broken at any point between the client and the server. Cases logged to Technical Support have been traced to issues with switches, proxy servers, SSL accelerators and loadbalancers. Note that these errors are reported more accurately in SilkPerformer 5.x than 4.x, so it is possible that tests than ran without error in 4.x will begin to report this error in tests using 5.x. Effect on the end-user: The effect on the end user could be anything from almost imperceptible to critical. Consider the difference between closing a connection while downloading spacer.gif versus the site homepage. Without further investigation it is impossible to say and a careful study of the replay log and TrueLog on Error files need to be made. This will show exactly what the users experiencing such errors would see. The HTTP 1011 error often occurs proceeded by a SSL security warning: WebPageUrl(Security: 267 - wrong version number, SSLRecv() failed) WebPageUrl(HTTP: 1011 - unexpected connection close during read., recv()) This is usually the result of a component (e.g loadbalancer) sending an incorrect (corrupted) SSL version number, which leads to the Security: 267 - wrong version number, and subsequent connection close. Old KB# 19244
↧