title: Jmeter 2.10 and 2.11 don't let me start a HTTP Script Recorder
body: <p>I'm having trouble starting a proxy server for jmeter 2.10 and 2.11.  I found a couple links <a href="https://stackoverflow.com/questions/19550472/jmeter-2-10-http-recorder-throws-keytool-exception">here on SO</a> and <a href="https://wiki.apache.org/jmeter/TestRecording210" rel="nofollow noreferrer">apache.org</a> but my error message is slightly different that what's written on these links.  Per the wiki from apache.org, I don't think I have trouble finding <code>keytool</code> because it returns the path when I do a </p>
  
  <pre><code>which keytool
  /usr/bin/keytool
  </code></pre>
  
  <p>and  I don't have trouble creating a file in the jmeter-210 and jmeter-211/bin dirs.  This is the error message I get in my jmeter.log file:</p>
  
  <pre><code>ERROR - jmeter.protocol.http.proxy.ProxyControl: Could not initialise key store java.io.IOException: Command :'"keytool" "-genkeypair" "-alias" ":root_ca:" "-dname" "CN=_ DO NOT INSTALL unless this is your certificate (JMeter root CA), OU=Username: COMPANY\user.name, C=US" "-keyalg" "RSA" "-keystore" "proxyserver.jks" "-storepass" "randomstr1" "-keypass" "randomstr1" "-validity" "7" "-ext" "bc:c"' failed, code: 1
  keytool error: java.io.IOException: Invalid escaped character in AVA: 's'
  </code></pre>
  
  <p>I don't know what this "invalid escaped char in AVA" is.  My company and username don't have the string "AVA" and I didn't find it in any of the property files in jmeter-21x/bin.</p>
  
  <p>Not sure if this is affecting it but I'm running jmeter from Darwin on a MBP, OSX 10.7.5.
  JMeter 2.9 doesn't give me any proxy issues, although, I ran into other issues with it, which is why I tried using these 2 newer versions, which are giving me problems with the proxy server.  I'll try going down to 2.8 to see what happens but I'd rather not if I can help it.  That and I'm super curious what the issue is with 2.1x and my laptop.  Thanks in advance for your help.</p>
  
  <p><strong>EDIT</strong>: The COMPANY/user.name part of the error message was changed this way to sanitize the error message, although, I will try at home on my linux box to see if the funny username representation is the cause.</p>