Threads never released after deployment
Test Case:
- Deploying an isac scenario on 100 clif servers. After the normal execution cycle (deployment, initialize, start, running, stop), the thread initially created during the deployment are not stopped. Say if 100 clif servers are used, the CLIF Console creates and never releases the 100 threads created. This is observable with the jconsole.
- Consequently, every time we deploy/init/run a scenario, the number of live threads in the console increases by the number of clif servers.
- It seems (to be confirmed) that each thread is blocking on a TCP connection (as shown by stack traces in the jconsole).