Hello, im (still) using JMeter 5.0 and got a test plan with a keystore (with only one cert), a http request default (where i have defined my https server and port).In the system.properties ive enabled the ssl debug for: sslcontext, session. Now i have one thread (loop only once) with 20 HTTPs POST-calls to my webserver - and now here is my problem. I see a CONNECT and i see the whole ssl-handshake stuff running perfectly.I see the POST and the data which is sent to my server (only few bytes)I see a client close And this runs for all 20 calls.
In my console i see:System property jdk.tls.client.cipherSuites is set to 'null' System property jdk.tls.client.cipherSuites is set to 'null'trigger seeding of SecureRandomdone seeding SecureRandom%% No cached client session%% Initialized: [Session-1, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384]%% Cached client session: [Session-1, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384]Test 1-1: setSoTimeout(0) calledTest 1-1: called close()Test 1-1: called closeInternal(true)Test 1-1: SEND TLSv1.2 ALERT: warning, description = close_notifyTest 1-1: called closeSocket(true)%% Cached client session: [Session-1, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384]%% Try resuming: [Session-1, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384] from Port 43434%% Invalidated: [Session-1, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384] And now JMeter start a new Session (Session-2) with all stuff and this for all 20 calls. Do anyone can help me how i can force JMeter to reuse the SSL-Session?I want to have one Session - then 20 calls - then a close. It seems that it's JMeter who force the close it's NOT my Webserver. I've tried with curl and it worked perfectly. Btw.I'm using java jre 9.0.4+11 on a linux client. thanks in advice for your help.
