On 29/09/05, Sylu <[EMAIL PROTECTED]> wrote: > Hi, > > I am running some jmeter tests and obtaining the results in the .CSV file. > The csv file shows some Non Http response codes as failures on some URLs in > the work flow. This is very inconsistent and appears on any of the URI at > any time. I am not able to make out the root cause of this. I am going > through the secure layers. I have suspected the keep alives and have no > longer enabled them in my jmeter script files, however these failures > persist.
Keep alive probably does not work with the default HTTPS implementation. > > The Jmeter logs just indicate either of the following messages when the non > - http response results. "non-HTTP response" means that an error has occured. There is no HTTP response that can be extracted from the returned data - there may indeed be no returned data. This is different from an error such as 404, where the reply contains HTTP data that can be parsed to extract the HTTP response. > 1. java.io.IOException Perhaps the remote server disconnected you. > 2. Connection failed, giving up > 3. Stop thread detected by thread Thread Group thread_group_name - > threadNumber That's presumably because you have set "Stop Thread on Error" > Can any one explain me what is a non http response and how can i eliminate Fix the server problem ... > that. And what is an IO Exception in the jmeter perspective when i get a non > http response. A run time error generated as a result of some failure. > Thanks in advance for the help. > NS > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
