In real env. I found some user's agents(mostly they are running in the VM) doesn't stop even when test is finished.
The agent is still assigned to the console port and continuously shows 100 % CPU rate.
I think it's because some grinder message is missing due to Network congestion problem.
We need to confirm that agent is well finished.
So I'm adding followings.
1. Agent is continuously informed with StopMessage every 5 seconds (In total 4 times maximum)
2. If it is not stopped well, send AgentController to stop agent. (1 time)