Gatling hangs when shutting down connection pool on initialization

Gatling (Open-Source)
1

Hi! I am seeing a recurring issue where Gatling gets stuck on start up trying to shut down the connection pool. This happens consistently after 4 previous Gatling tests of about 36k connections each are run. The 5th test is the one that hangs.
Any ideas how to resolve this?
Here is the console output I am seeing:

21:58:07 2019-03-25 17:58:06,904 INFO - Gatling will try to use 'gatling.conf' as custom config file.
21:58:07 2019-03-25 17:58:07,437 INFO - Slf4jLogger started
21:58:10 2019-03-25 17:58:10,502 INFO - Shutting down connection pool: curAllocated=0 idleQueues.size=0 waitQueue.size=0 maxWaitQueueLimit=256 closed=false
21:58:13 2019-03-25 17:58:13,547 INFO - Shutting down connection pool: curAllocated=1 idleQueues.size=1 waitQueue.size=0 maxWaitQueueLimit=256 closed=false
21:58:14 2019-03-25 17:58:13,928 INFO - Shutting down connection pool: curAllocated=1 idleQueues.size=1 waitQueue.size=0 maxWaitQueueLimit=256 closed=false
21:58:14 2019-03-25 17:58:14,299 INFO - Shutting down connection pool: curAllocated=1 idleQueues.size=1 waitQueue.size=0 maxWaitQueueLimit=256 closed=false
21:58:17 2019-03-25 17:58:16,854 INFO - Shutting down connection pool: curAllocated=1 idleQueues.size=1 waitQueue.size=0 maxWaitQueueLimit=256 closed=false
21:58:18 2019-03-25 17:58:17,229 INFO - Shutting down connection pool: curAllocated=1 idleQueues.size=1 waitQueue.size=0 maxWaitQueueLimit=256 closed=false
21:58:20 2019-03-25 17:58:19,912 INFO - Shutting down connection pool: curAllocated=1 idleQueues.size=1 waitQueue.size=0 maxWaitQueueLimit=256 closed=false
21:58:20 2019-03-25 17:58:20,100 INFO - Shutting down connection pool: curAllocated=1 idleQueues.size=1 waitQueue.size=0 maxWaitQueueLimit=256 closed=false

2

Hi,

This log has nothing to do with any official Gatling component.
It comes from http4s, which Gatling doesn’t use.
You’re most likely using some private custom component and it’s broken.

3

Ah, okay thanks, that makes sense! I'll take a look at which component might be causing it.