| Summary: | Cannot run program "keytool": CreateProcess error=2 when starting JMeter 3.2 in gui mode | ||
|---|---|---|---|
| Product: | JMeter - Now in Github | Reporter: | Anthony Kearns <anthony> |
| Component: | Main | Assignee: | JMeter issues mailing list <issues> |
| Status: | VERIFIED FIXED | ||
| Severity: | normal | CC: | anthony |
| Priority: | P2 | ||
| Version: | 3.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Attachments: | Jmeter Log File | ||
Thank you for your report. This not an issue, JMeter try several ways to find the keytool util. The error message just say that JMeter don't find keytool util from PATH environment variable. After JMeter finally found keytool from JAVA_HOME variable, so the keystore can be generated with success. So JMeter 3.2 despite the -not-error message will work correctly on your machine. I've change this message from the level ERROR to INFO to avoid this (false) error message (and move the stacktrace into DEBUG level). Thanks URL: http://svn.apache.org/viewvc?rev=1792359&view=rev Log: Cannot run program "keytool": CreateProcess error=2 when starting JMeter 3.2 in gui mode Change level (from ERROR to INFO) of the exception message when JMeter try to find the keytool util from PATH env var. It's not a error because JMeter try to find keytool with several ways. Little code format to allow better code review. Bugzilla Id: 61026 Modified: jmeter/trunk/src/jorphan/org/apache/jorphan/exec/KeyToolUtils.java jmeter/trunk/xdocs/changes.xml This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/4375 |
Created attachment 34940 [details] Jmeter Log File Today i downloaded the new JMeter 3.2 build and tried to start it in gui mode e.g. ran the jmeter.bat from the bin folder. JMeter started but i noticed there were errors in the log viewer. Please see the attached file for the exception details and my system details etc. I do not have any third party plugins etc installed. I just literally downloaded and extracted and tried to run in user and admin mode.