DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=42819>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=42819 ------- Additional Comments From [EMAIL PROTECTED] 2007-07-06 04:50 ------- (In reply to comment #5) > Hi Sebastian > Thanks for your various suggestions and comments. I > tried them out and came up with the following results: > > You can try defining the jmeter property: > > https.sessioncontext.shared=true > > to revert to the previous behaviour. > > What happens if you try that? > I can see no difference, the NPE is still there. Yes, that was intended as a fix for reverting to the original SSL behaviour, not the NPE. > > Try setting the system property: > > javax.net.ssl.keyStorePassword > > to an empty string - the NPE should disappear. > > Does this fix the NPE for you? > No, unfortunately it doesn't either. You need to set the property in system.properties or otherwise ensure that it is defined very early on. > > Alternatively, delete the keystore file (unless you need it). > Now this does seem to work; the NPE is no longer showing in the > log file, and the problematic test plan is running faster by > about the factor 6. On the other hand, I do need the file for > other purposes, but for the time being, I can use this workaround. Rather than use the keystore from the default location, use the system.properties entry: javax.net.ssl.keyStore to define the appropriate location, and make sure the password is also defined. > > The problem also occurs on JMeter 2.2, so the bug has been > > lurking for a little while ... > If this is the case, then there must be some other difference > in the code preventing the NPE to be thrown in version 2.2 > because I am not getting any stack trace in the 2.2 log file > (Or the NPE is sensibly handled or simply not logged). That's odd. For it to occur, the following needs to be true: * using SSL * keystore file is found * no password provided * non-GUI mode Perhaps your 2.2 setup provides a password? What happens if you run the SSL test in GUI mode in 2.2? Do you get a password prompt? I do (if there is a keystore but no password defined), and pressing cancel or X rather than OK also produces the NPE. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
