[Bug 62940] Unable to record IP based URL
https://bz.apache.org/bugzilla/show_bug.cgi?id=62940 --- Comment #1 from gsm...@gmail.com --- I have used different version of jdk and I'm getting the same result. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 62940] New: Unable to record IP based URL
https://bz.apache.org/bugzilla/show_bug.cgi?id=62940
Bug ID: 62940
Summary: Unable to record IP based URL
Product: JMeter
Version: 4.0
Hardware: PC
Status: NEW
Severity: blocker
Priority: P2
Component: HTTP
Assignee: issues@jmeter.apache.org
Reporter: gsm...@gmail.com
Target Milestone: JMETER_5.1
Hi Team,
When I try to record HTTPS based site which have IP rather DNS and I could see
the log from jmeter as below.
java.io.IOException: >> keytool error: java.lang.RuntimeException:
java.io.IOException: DNSName components must begin with a letter <<
Command failed, code: 1
'keytool -genkeypair -alias 10.32.120.143 -dname "cn=10.32.120.143, o=JMeter
Proxy (TEMPORARY TRUST ONLY)" -keyalg RSA -keystore proxyserver.jks -storepass
{redacted} -keypass {redacted} -validity 7 -ext san=dns:10.32.120.143'
at
org.apache.jorphan.exec.KeyToolUtils.genkeypair(KeyToolUtils.java:171)
~[jorphan.jar:4.0 r1823414]
at
org.apache.jorphan.exec.KeyToolUtils.generateSignedCert(KeyToolUtils.java:285)
~[jorphan.jar:4.0 r1823414]
at
org.apache.jorphan.exec.KeyToolUtils.generateHostCert(KeyToolUtils.java:276)
~[jorphan.jar:4.0 r1823414]
at
org.apache.jmeter.protocol.http.proxy.ProxyControl.updateKeyStore(ProxyControl.java:1563)
~[ApacheJMeter_http.jar:4.0 r1823414]
at
org.apache.jmeter.protocol.http.proxy.Proxy.getSSLSocketFactory(Proxy.java:324)
[ApacheJMeter_http.jar:4.0 r1823414]
at org.apache.jmeter.protocol.http.proxy.Proxy.startSSL(Proxy.java:429)
[ApacheJMeter_http.jar:4.0 r1823414]
at org.apache.jmeter.protocol.http.proxy.Proxy.run(Proxy.java:194)
[ApacheJMeter_http.jar:4.0 r1823414]
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 62940] Unable to record IP based URL
https://bz.apache.org/bugzilla/show_bug.cgi?id=62940 gsm...@gmail.com changed: What|Removed |Added CC||gsm...@gmail.com OS||All -- You are receiving this mail because: You are the assignee for the bug.
[Bug 62941] New: Transaction Controller : ORed aggregation of statuses, to ease "Retry request N times on fail" test implementation
https://bz.apache.org/bugzilla/show_bug.cgi?id=62941 Bug ID: 62941 Summary: Transaction Controller : ORed aggregation of statuses, to ease "Retry request N times on fail" test implementation Product: JMeter Version: 5.0 Hardware: PC Status: NEW Severity: enhancement Priority: P3 Component: Main Assignee: issues@jmeter.apache.org Reporter: avam0ns...@gmail.com Target Milestone: JMETER_5.0 Transaction Controller enhancement - make user specify transaction status aggregation rules from child sampler's statuses. Currently transaction is successful when ALL child samplers are successful. (AND rule) I suggest to add the "OR aggregation" checkbox to Transaction Controller UI, meaning that transaction is successful when there is at least one successful child sampler. This checkbox should be unchecked by default. This will help to implement the "http retry" much easier that it is possible today. Check this Frankenstein for example (not working in Jmeter5 btw): https://www.blazemeter.com/blog/how-to-count-retries-as-a-single-request-in-jmeter What I'm trying to achieve, is having these "OR-aggregated" transactions in Jmeter reports as successful, when a sequence of failed child samplers requests ended up with successful one. With transaction time still being the total of all child samplers time, as it is now. And I still want to have proper success/fail statuses for child samplers within the transaction. -- You are receiving this mail because: You are the assignee for the bug.
