0

I have done execution in jmeter tool in two differnent environment and found huge variation in reponse time .For ENV1 i am getting nearly 3sec and for ENV2 it is comming < 1 sec.I checked in logs and found api logs are not taking much time only For secure session establishment(SSL Certificate) it is taking time.Please help, will really appreciate if it's explained in details.(Attaching log details of both the environment)

ENV1 log details:

2019-07-31 14:55:27,532 DEBUG o.a.j.u.JsseSSLManager: keyType: RSA 2019-07-31 14:55:27,532 DEBUG o.a.j.u.JsseSSLManager: Client alias: '1' 2019-07-31 14:55:27,532 DEBUG o.a.j.u.JsseSSLManager: WrappedX509Manager: getCertificateChain(1) 2019-07-31 14:55:27,532 DEBUG o.a.j.u.JsseSSLManager: WrappedX509Manager: getPrivateKey: sun.security.rsa.RSAPrivateCrtKeyImpl@ffef9391 ****2019-07-31 14:55:29,664 DEBUG o.a.h.c.s.SSLConnectionSocketFactory: Secure session established 2019-07-31 14:55:29,664 DEBUG o.a.h.c.s.SSLConnectionSocketFactory: negotiated protocol: TLSv1.2 2019-07-31 14:55:29,664 DEBUG o.a.h.c.s.SSLConnectionSocketFactory: negotiated cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA 2019-07-31 14:55:29,664 DEBUG o.a.h.c.s.SSLConnectionSocketFactory: peer principal: CN=7dkUc8BjHPYgSadbvt2Ysr, OU=0015800000jfQ9aAAE, O=OpenBanking, C=GB 2019-07-31 14:55:29,664 DEBUG o.a.h.c.s.SSLConnectionSocketFactory: issuer principal: CN=OpenBanking Pre-Production Issuing CA, O=OpenBanking, C=GB 2019-07-31 14:55:29,664 DEBUG o.a.j.p.h.s.HTTPHC4Impl$JMeterDefaultHttpClientConnectionOperator: Connection established 10.102.45.126:65254<->3.121.54.161:443 2019-07-31 14:55:29,664 DEBUG o.a.h.i.e.MainClientExec: Executing request POST /oauth/as/token.oauth2? HTTP/1.1

While in ENV2 it is coming in millisecond.

2019-07-31 15:52:06,371 DEBUG o.a.j.u.JsseSSLManager: keyType: RSA 2019-07-31 15:52:06,371 DEBUG o.a.j.u.JsseSSLManager: Client alias: '1' 2019-07-31 15:52:06,371 DEBUG o.a.j.u.JsseSSLManager: WrappedX509Manager: getCertificateChain(1) 2019-07-31 15:52:06,371 DEBUG o.a.j.u.JsseSSLManager: WrappedX509Manager: getPrivateKey: sun.security.rsa.RSAPrivateCrtKeyImpl@ffef9391 2019-07-31 15:52:06,516 DEBUG o.a.h.c.s.SSLConnectionSocketFactory: Secure session established 2019-07-31 15:52:06,516 DEBUG o.a.h.c.s.SSLConnectionSocketFactory: negotiated protocol: TLSv1.2 2019-07-31 15:52:06,516 DEBUG o.a.h.c.s.SSLConnectionSocketFactory: negotiated cipher suite: TLS_RSA_WITH_AES_256_CBC_SHA 2019-07-31 15:52:06,517 DEBUG o.a.h.c.s.SSLConnectionSocketFactory: peer principal: CN=7dkUc8BjHPYgSadbvt2Ysr, OU=0015800000jfQ9aAAE, O=OpenBanking, C=GB 2019-07-31 15:52:06,517 DEBUG o.a.h.c.s.SSLConnectionSocketFactory: issuer principal: CN=OpenBanking Pre-Production Issuing CA, O=OpenBanking, C=GB 2019-07-31 15:52:06,517 DEBUG o.a.j.p.h.s.HTTPHC4Impl$JMeterDefaultHttpClientConnectionOperator: Connection established 10.102.45.126:49546<->34.246.60.233:443 2019-07-31 15:52:06,517 DEBUG o.a.h.i.e.MainClientExec: Executing request POST /oauth/as/token.oauth2 HTTP/1.1

  • 2
    Yours logs show only what you have logged - other (hidden) factors may have come into place. Can you explain the configuration of these environments? – João Farias Aug 30 at 7:02
0
  1. To get more information on what's going on under the hood you can add the next line to system.properties file

    javax.net.debug=ssl
    
  2. You can also consider disabling closing connection on each Thread Group iteration so JMeter will keep the session between iterations therefore SSL handshake will happen only once. Add the next line to user.properties file:

    httpclient.reset_state_on_thread_group_iteration=false

Additional information:

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.