[ https://issues.jboss.org/browse/MODCLUSTER-536?page=com.atlassian.jira.pl... ] Wayne Wang edited comment on MODCLUSTER-536 at 9/1/16 12:08 PM: ---------------------------------------------------------------- The lsof command used for wildfly instance in one virtualbox vm was lsof -u wayne | grep TCP | wc -l The wildfly instance was started under user wayne. I can also find out the pid of the wildfly instance and change the command to lsof -p <pid> | grep TCP | wc -l. However, the result will be the same, so it was convenient for me to use the -u command The lsof command used for apache web server in another virtualbox vm was lsof -u daemon | grep TCP | wc -l I also use the following to monitor the outcome of the command watch -n 5 'lsof -u wayne | grep TCP |wc -l' (1) if there was no shutdown of wildfly instance, the outcome of the command will keep low (about 200) and does not show the pattern of steady increase (2) if I shut down the wildfly instance and let another standby instance to become active, and do this multiple times, I will see the outcome of the command show steady increase, and when it reach > 3000, server will print out error. The Apache web server needs to be restarted in order to support another load test. The wildfly instance also needs to be restarted due to the error of "Too many open files" and the outcome of lsof command remains high and unchanged. Note the soft limit was set at 4096 and hard limit was set at 8192 was (Author: wwang2016): The lsof command used for wildfly instance in one virtualbox vm was lsof -u wayne | grep TCP | wc -l The wildfly instance was started under user wayne. I can also find out the pid of the wildfly instance and change the command to lsof -p <pid> | grep TCP | wc -l. However, the result will be the same, so it was convenient for me to use the -u command The lsof command used for apache web server in another virtualbox vm was lsof -u daemon | grep TCP | wc -l I also use the following to monitor the outcome of the command watch -n 5 '${the above command}' (1) if there was no shutdown of wildfly instance, the outcome of the command will keep low (about 200) and does not show the pattern of steady increase (2) if I shut down the wildfly instance and let another standby instance to become active, and do this multiple times, I will see the outcome of the command show steady increase, and when it reach > 3000, server will print out error. The Apache web server needs to be restarted in order to support another load test. The wildfly instance also needs to be restarted due to the error of "Too many open files" and the outcome of lsof command remains high and unchanged. Note the soft limit was set at 4096 and hard limit was set at 8192 -- This message was sent by Atlassian JIRA (v6.4.11#64026)