On 5/31/05, Major, Michael T <[EMAIL PROTECTED]> wrote: > This is all that I saw in the DOS dialog box: > > [Full GC 93241K->9044K(249088K), 0.2957412 secs] > > Which I believe is normal. I removed some of the ResultCollectors, but > like you said, it didn't make any changes.
Yes, it is normal. > From the result tree that you recommended, I get pretty much the same > error that I was always getting: > > On the Sampler Result tab I get the following: > > Load time: 222871 > HTTP response code: Non HTTP response code > HTTP response message: Non HTTP response message > > HTTP response headers: > > On the Response data tab, I get the following error: > java.net.SocketException: Unexpected end of file from server > at > sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:684) > at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:554) > at > sun.net.www.protocol.http.HttpURLConnection.doTunneling(HttpURLConnectio > n.java:1257) > at > sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:678)........ [It would be useful to have the rest of the trace with the JMeter classes.] That's the bit that was missing - it explains why JMeter reported non-HTTP response code. Not sure why it does not appear in jmeter.log. What appears to be happening is that the JVM http client code is trying to read a header and getting end of data from the server. > I just don't understand why I would be able to get to the home login > page, and yet not be able to test the actual login. Yet when I run the > test outside of our company network (no proxy) the tests run perfectly. Could be a fault with the proxy or the server that has been triggered by something JMeter sent or did not send. If you are using keep-alive it might be worth switching it off or vice-versa. > I am pretty much stuck. Is there a way that you can turn on more > logging for the HTTPSampler? Yes, either put -Ljmeter.protocol.http=DEBUG on the jmeter command line or add the following to jmeter.properties: log_level.jmeter.protocol.http=DEBUG However, this may not generate enough information. If you switch to using Apache HttpClient, you can turn on wire debugging - see jmeter.properties for details. You'll need to replace all the samplers - a quick hack is to replace sampler.HTTPSampler with sampler.HTTPSampler2 and gui.HttpTestSampleGui with gui.HttpTestSampleGui2 throughout the JMX file. S. > Thank you in advance, > > Mike Major > > -----Original Message----- > From: sebb [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 31, 2005 11:17 AM > To: Major, Michael T > Cc: JMeter Users List > Subject: Re: Jmeter HTTPS testing through proxy > > > On 5/31/05, Major, Michael T <[EMAIL PROTECTED]> wrote: > > > > > > Thank you for the quick reply. I don't see anything unusual in the > > jmeter.log. I have added the results to the bottom of this email. > > Also, when I go to the site and login via IE, I have no problems with > > the proxy. > > > > Any other ideas? > > > > Thank you again, > > > > Mike > > > > > > One thing is clear - the default logging levels need to be adjusted in > some of the classes ... > > I don't understand why there was not some more information from > HTTPSampler regarding the nonHTTP response code. > > I suppose it's possible that some errors are still being directed to the > console instead of the log file - did you see anything in the DOS > console box? > > Might be worth adding a View Tree Listener, and checking for any further > information in that. > > There also seem to be quite a lot of ResultCollectors in the test plan > - not that this should affect things. > > S. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
