Version
2.11.0
Bug description
KeyExchangeMessageHandler:89 creates an unnamed SingleThreadExecutor, which is kept open for each session.
In our use case we create connections to several thousand servers and keep them open.
Would it be possible to close this pool more eagerly?
If not or too complicated, a single instance pool, which ideally could be configured, would probably also work.
Actual behavior
Threads stay alive
Expected behavior
Pool is closed more eagerly
Relevant log output
2024-01-24 15:18:42,094 INFO session.ClientSessionImpl: flushQueue(ClientSessionImpl[...:22]): 3 pending packets to flush [pool-3231-thread-1]
Other information
No response
Version
2.11.0
Bug description
KeyExchangeMessageHandler:89creates an unnamed SingleThreadExecutor, which is kept open for each session.In our use case we create connections to several thousand servers and keep them open.
Would it be possible to close this pool more eagerly?
If not or too complicated, a single instance pool, which ideally could be configured, would probably also work.
Actual behavior
Threads stay alive
Expected behavior
Pool is closed more eagerly
Relevant log output
Other information
No response