[ https://issues.jboss.org/browse/MODCLUSTER-536?page=com.atlassian.jira.pl... ] Wayne Wang edited comment on MODCLUSTER-536 at 8/31/16 11:35 AM: ----------------------------------------------------------------- Additional information: I could shut down the instance in two different ways during load tests (1) After Jmeter send button is back (all requests were sent to a specific wildfly instance for processing) (2) Before Jmeter send button is back, and the rest of requests need to be routed to the soon-to-be active wildfly instance that is currently inactive. I found one round of load test with the second way of shutting down the wildfly instance will cause the "Too many open files" issue in the next round of load test. If I use the first way of shutting down the wildfly instance, it needs three times of load tests to replicate the issue. So it looks like shutting down a wildfly instance may be one potential cause of the issue. In addition, the activation of the standby instance takes some time, and the rest of requests will go nowhere during that period of time until the standby instance becomes active. I am not sure if this can bring additional issue was (Author: wwang2016): Additional information: I could shut down the instance in two different ways during load tests (1) After Jmeter send button is back (all requests were sent to a specific wildfly instance for processing) (2) Before Jmeter send button is back, and the rest of requests need to be routed to the soon-to-be active wildfly instance that is currently inactive. I found one round of load test with the second way of shutting down the wildfly instance will cause the "Too many open files" issue in the next round of load test. If I use the first way of shutting down the wildfly instance, it needs three times of load tests to replicate the issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)