TCPServer and ThreadPool management

[DKL72]

Hello:

I create a TCPServer and pass it a ThreadPool of say minCapacity = 1, maxCapacity = 3. The TCPServer accepts 3 clients so the thread pool shows allocated = 3, used = 3, available = 0. Now I disconnect all 3 clients from the TCPServer. The thread pool still shows allocated = 3, used = 3, available = 0 so I can no longer handle new clients that connect. I tried calling "collect" on the thread pool and it doesn't help. What am I doing wrong?

Thank you.

[alex]

What does TCPServer::currentConnections() return?

[DKL72]

TCPServer::currentConnections() returns 0 after dropping the 3 connections.

[DKL72]

TCPServer::currentConnections() returns 0 after dropping the 3 connections.

Also, TCPServer::currentThreads() shows 3 (even though currentConnections shows 0).

[guenter]

Are you sure your TCPServerConnection::run() method returns when the client closes the connection?

[DKL72]

Are you sure your TCPServerConnection::run() method returns when the client closes the connection?

Yes, just confirmed it. I guess a good place for me to debug is inside the TCPServerDispatcher::run() and step through to see what happens after it returns.

[alex]

Default thread idle time is 10 seconds. You may want to experiment with different values for TCPServerParams::setThreadIdleTime() and/or wait for a while before checking currentThreads().