I also get NPE errors in jmeter.log in non-GUI mode. However, if I edit jmeter.properties and define
javax.net.ssl.keyStorePassword=xyzxyz the NPE goes away, and the test seems to work OK - also then the GUI does not prompt either. It does not seem to matter if the password to the keystore is wrong - an error is logged, but the sample works anyway. I used https://www.host.com/ for the base URL in the Authorization Manager. The NPE error in non-GUI mode is a bug. But hopefully if you define the keystore password your test will work in non-GUI mode. S. On Thu, 20 Jan 2005 19:48:57 -0600, Stephen Charles Huey <[EMAIL PROTECTED]> wrote: > I see that there's a bug listed here that was opened in 2003: > http://issues.apache.org/bugzilla/show_bug.cgi?id=25505 > > I've also read messages like this one: > http://mail-archives.apache.org/eyebrowse/[EMAIL PROTECTED]&msgId=1396031 > > I'm not sure how related it is to my problem, because the posts there > suggest that the problem goes away after the first HTTPS request, but > that's not the case for me! I'm using JMeter 2.0.2 with JVM 1.4.2_03 > and I can't connect to HTTPS URLs on our test servers. The log tells me > stuff like "java.io.IOException: HTTPS hostname wrong" and this: > responseMessage="Non HTTP response message" > > The problem ONLY OCCURS when I run it in non-GUI mode. However, I've > noticed that despite the fact that I have an HTTP Authorization Manager > that I believe is configured correctly, it often prompts me for my > keystore password when I run it in the GUI. Why is this? Could the > fact that my JMX file is not configured to already have this be the > reason it doesn't work in non-GUI mode, or are these two things not > really related? > > Why does it prompt me if I have an HTTP Authorization Manager with the > base URL (and for that base URL, I have entries for both http and https > just in case, because when you type in the name of our site, it prompts > you with a basic authentication box and then redirects you to an HTTPS > page). In addition to the base URL, I also have an https entry for our > base URL + the context base. For example: > http://www.baseURL.com > https://www.baseURL.com > https://www.baseURL.com/mainwebapp/ > > If that's not right, please let me know! I'd love to find out a way to > resolve this since I'm trying to do lots of testing right now (and from > behind different public IPs to trick the load balancing our site uses), > so consequently I'm very interested in getting the non-GUI one to work > with our test servers. However, if that's not going to be possible > right now, I guess I can just try to leave one open on a scheduler or > something. > > Thanks, > Stephen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]