[
https://issues.jboss.org/browse/MODCLUSTER-536?page=com.atlassian.jira.pl...
]
Wayne Wang commented on MODCLUSTER-536:
---------------------------------------
I have wildfly running in one virtualbox vm, and httpd running in another virtualbox vm.
They are running under different users (wildfly running under a user and httpd running
under root).
I would like to mention that this is a HA singleton configuration that I am testing.
During load tests, I would shut down the active wildfly instance, and it will fail over to
another standby instance. I saw the issue after a couple of such tests,
I am not sure if these tests could introduce issues to httpd connections with wildfly
instance. However, these test cases are expected scenarios in production. For example, we
need to shut down the active instance and do maintenance work and let the application fail
over to another standby instance.
Nevertheless, I will try to test the scenario where the wildfly instance is not shutdown,
and I load test through web server (httpd), and see if there is any issue.
List of open files grows steadily during load test through
mod_cluster
----------------------------------------------------------------------
Key: MODCLUSTER-536
URL:
https://issues.jboss.org/browse/MODCLUSTER-536
Project: mod_cluster
Issue Type: Bug
Components: Core & Container Integration (Java)
Affects Versions: 1.3.1.Final
Environment: Wildfly10.0.0.Final
mod_cluster-1.3.1.Final-linux2-x64-ssl
CentOS7 (virtualbox)
Reporter: Wayne Wang
Assignee: Michal Karm Babacek
Attachments: error_log, httpd-mpm.conf, httpd.conf, server.log,
standalone-full-ha-snippet.xml
I was able to configure wildfly 10 modcluster to work with Apache mod_cluster (1.3.1).
However, when I was doing a load test, I found out that the test through web server
eventually caused error in wildfly instance and I also saw error log in Apache web server
The obvious error in wildfly instance is the so-called "java.net.SocketException:
Too many files open". When I used the command lsop -u | grep TCP | wc -l, I can see
the number grew steadily until the wildfly instance reported the error. This was when I
sent requests through web server.
However, when I sent the requests through wildfly instance (app server) directly, the
number did not grow, and the app server can take a lot heavier load without this issue.
The issue did not happen until many rounds of load tests were executed through web
server. If I restart the web server, everything is working fine until I execute many
rounds of load tests again
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)