# j.n.s. SSLException handshake timeout

**URL:** <https://community.gatling.io/t/j-n-s-sslexception-handshake-timeout/5807>\
**Category:** Gatling (Open-Source)\
**Created:** [September 22, 2020, 7:34am UTC](https://community.gatling.io/t/j-n-s-sslexception-handshake-timeout/5807 "2020-09-22T07:34:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ganesh\_kakani1](https://avatars.discourse-cdn.com/v4/letter/g/c57346/32.png) [@ganesh\_kakani1](https://community.gatling.io/u/ganesh_kakani1)\
**Post date:** [September 22, 2020, 7:34am UTC](https://community.gatling.io/t/j-n-s-sslexception-handshake-timeout/5807/1 "2020-09-22T07:34:09Z")

</div>

Hi

Facing j.n.s. SSLException handshake timeout while running huge load.Is this only because of high number of requests.Any inputs on this?

---

<div class="post-metadata">

**Author:** ![slandelle](https://dub1.discourse-cdn.com/flex013/user_avatar/community.gatling.io/slandelle/32/4_2.png) [@slandelle](https://community.gatling.io/u/slandelle)\
**Post date:** [September 22, 2020, 7:36am UTC](https://community.gatling.io/t/j-n-s-sslexception-handshake-timeout/5807/2 "2020-09-22T07:36:27Z")

</div>

Gatling is only the messenger: your endpoint(s) in charge of TLS can’t handle such load and that’s something you have to fix (usually scale out to multiple endpoints with DNS round-robin).