https://issues.apache.org/bugzilla/show_bug.cgi?id=56057
Bug ID: 56057
Summary: JMeter does not create ApacheJMeterTemporaryRootCA.crt
when starting a recording
Product: JMeter
Version: 2.11
Hardware: PC
Status: NEW
Severity: major
Priority: P2
Component: HTTP
Assignee: [email protected]
Reporter: [email protected]
This issue was discovered in jMeter 2.10. It has been verified to still exist
in JMeter 2.11 (however expiration sub-issue has not been verified to still
exist in 2.11).
Configuration:
Windows 7.
jMeter 2.10 (upgraded to 2.11 during investigation).
C:\>java -version
java version "1.7.0_09"
Java(TM) SE Runtime Environment (build 1.7.0_09-b05)
Java HotSpot(TM) 64-Bit Server VM (build 23.5-b02, mixed mode)
Java executed from the command line calls:
C:\Program Files\Java\jdk1.7.0_09\bin\java.exe
JMETER_HOME points to the JMeter 2.10 installation base.
JAVA_HOME points to C:\Program Files\Java\jdk1.7.0_09
keytool.exe is on the path and resides in:
C:\Program Files\Java\jdk1.7.0_09\bin
The folder: %JMETER_HOME%\bin is writable and JMeter can write to it
(evidenced by creation of jmeter.log).
Summary Description:
JMeter reports creating an ApacheJMeterTemporaryRootCA certificate when
starting 'HTTP(S) Test Script Recorder'. First-time-through the
ApacheJMeterTemporaryRootCA.crt file is created. After expiration (only
verified in 2.10), or subsequent removal (JMeter 2.10 and JMeter 2.11) of the
ApacheJMeterTemporaryRootCA.crt (and ApacheJMeterTemporaryRootCA.usr in JMeter
2.11), JMeter reports creating an ApacheJMeterTemporaryRootCA certificate when
starting 'HTTP(S) Test Script Recorder', but does not.
Workaround:
JMeter 2.11: Remove the three files: ApacheJMeterTemporaryRootCA.crt,
ApacheJMeterTemporaryRootCA.usr, and proxyserver.jks. Start 'HTTP(S) Test
Script Recorder'.
(Note: as the .crt and .usr files were removed first, and after testing again,
the file proxyserver.jks was removed, it is not known if removing only the
proxyserver.jks file would result in a new .crt and .usr files being created)
(This workaround HAS NOT been verified to work in JMeter 2.10)
Detailed Investigation:
Originally using JMeter 2.10. When following the procedure for recording
http(s) at http://jmeter.apache.org/usermanual/jmeter_proxy_step_by_step.pdf,
at the point when starting the 'HTTP(S) Test Script Recorder', a pop-up informs
the user:
Root CA Certificate: ApacheJMeterTemporaryRootCA created in JMeter
bin directory (etc., etc.…)
In this circumstance first-time-through, the certificate
ApacheJMeterTemporaryRootCA.crt was created and used successfully.
Subsequently, after the expiration of the generated certificate, the same
procedure was attempted. JMeter reports that it has generated a new
certificated, but no new certificate was created.
The file ApacheJMeterTemporaryRootCA.crt was then removed and the procedure was
repeated. Again, JMeter reports that it has generated a new certificated, but
no new certificate was created.
In the jmeter.log during this procedure, at the point when starting the
'HTTP(S) Test Script Recorder', an entry is written to the log such as:
2014/01/22 13:58:57 WARN - jmeter.protocol.http.proxy.ProxyControl:
Problem reading key storeNotAfter: Tue Jan 07 09:12:09 MST 2014
Except for the WARN in the log, JMeter behaves as if it has created the .crt
file, but it does not.
It was learned that there was a version 2.11 that addressed some issues
regarding errors relating to the .crt file. The 2.11 release was installed and
first-time-use produced an ApacheJMeterTemporaryRootCA.crt file as expected.
Additionally a file ApacheJMeterTemporaryRootCA.usr was also created. The .crt
file worked as expected in the browser.
To test repeatability, the .crt and .usr were removed and the test was
repeated. Upon start of the 'HTTP(S) Test Script Recorder', NO new .crt or .usr
file was created. There was NO WARN reported to the log as in 2.10.
A careful comparison of the original installation bin files with the current
installation revealed that an additional file proxyserver.jks had been created.
Repeating the proceedure after removal of this file in addition to the .crt and
.usr files, produces a new .crt file.
--
You are receiving this mail because:
You are the assignee for the bug.
