]
Jean-Frederic Clere edited comment on MODCLUSTER-536 at 8/31/16 4:34 AM:
-------------------------------------------------------------------------
mod_cluster persists the connections between httpd and wilfly to reuse them. Basically you
need to make sure the user daemon has a ulimit -n big enough to deal with the number of
connection. once the max file is reached httpd might not cover well :-(
Looking in httpd-mpm.conf (MaxRequestWorkers 400) basically you are going to have at
least 800 files open, very neat to 1024 default limit.
Is wildfly runned in the same user?
was (Author: jfclere):
mod_cluster persists the connection between httpd and wilfly to reuse them. Basically you
need to make sure the user daemon has a ulimit -n big enough to deal with the number of
connection. once the max file is reached httpd might not cover well :-(
Looking in httpd-mpm.conf (MaxRequestWorkers 400) basically you are going to have at
least 800 files open, very neat to 1024 default limit.
Is wildfly runned in the same user?
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