Re: RFR: 8350705: [JMH] test security.SSLHandshake failed for 2 threads configuration

2025-04-08 Thread Daniel Jeliński
On Mon, 24 Mar 2025 12:54:01 GMT, Daniel Jeliński wrote: > Update the SSLHandshake benchmark to enable running in multiple threads. > > This PR changes the scope of the state from per-benchmark to per-thread. The > server SSLContext is still shared across all threads to simulate the scenario >

Re: RFR: 8350705: [JMH] test security.SSLHandshake failed for 2 threads configuration

2025-04-08 Thread Sean Mullan
On Mon, 24 Mar 2025 12:54:01 GMT, Daniel Jeliński wrote: > Update the SSLHandshake benchmark to enable running in multiple threads. > > This PR changes the scope of the state from per-benchmark to per-thread. The > server SSLContext is still shared across all threads to simulate the scenario >

Re: RFR: 8350705: [JMH] test security.SSLHandshake failed for 2 threads configuration

2025-04-05 Thread Daniel Jeliński
On Tue, 25 Mar 2025 15:38:02 GMT, Hai-May Chao wrote: >> Update the SSLHandshake benchmark to enable running in multiple threads. >> >> This PR changes the scope of the state from per-benchmark to per-thread. The >> server SSLContext is still shared across all threads to simulate the >> scenar

Re: RFR: 8350705: [JMH] test security.SSLHandshake failed for 2 threads configuration

2025-03-25 Thread Hai-May Chao
On Mon, 24 Mar 2025 12:54:01 GMT, Daniel Jeliński wrote: > Update the SSLHandshake benchmark to enable running in multiple threads. > > This PR changes the scope of the state from per-benchmark to per-thread. The > server SSLContext is still shared across all threads to simulate the scenario >

RFR: 8350705: [JMH] test security.SSLHandshake failed for 2 threads configuration

2025-03-24 Thread Daniel Jeliński
Update the SSLHandshake benchmark to enable running in multiple threads. This PR changes the scope of the state from per-benchmark to per-thread. The server SSLContext is still shared across all threads to simulate the scenario where multiple clients try to connect to the same server at the same