When clinet connecting again, there is a new ThreadPool..
Posted: 30 May 2018, 05:21
We detect client whether it is lose connection. If client lose connection, we use Sfsclient.connect again.
If connection is still not be establish, the job keep using Sfsclient.connect again.
We discover a Thread Pool created after using Sfsclient.connect.
So the worst situation is client program will be out of memory because there are so many Thread Pool that created by SfsClient in JVM.
Cloud you inspire me what is the explicit way to implement sfsclient reconnecting? No redundant thread pool existing .
If connection is still not be establish, the job keep using Sfsclient.connect again.
We discover a Thread Pool created after using Sfsclient.connect.
So the worst situation is client program will be out of memory because there are so many Thread Pool that created by SfsClient in JVM.
Cloud you inspire me what is the explicit way to implement sfsclient reconnecting? No redundant thread pool existing .