[
https://issues.jboss.org/browse/MODCLUSTER-536?page=com.atlassian.jira.pl...
]
Wayne Wang commented on MODCLUSTER-536:
---------------------------------------
The default value of MaxClients =150
The default value of MaxRequestWorkers = 400
The default values are quite different although those two parameters mean the same thing.
I have tested in v1.2.6 with MaxClients set to 200, 250, and I did not see server error
although I saw the number of messages being processed actually got decreased. I found the
MaxClients set to 50 actually results in much more requests being successfully processed.
Not sure if I change MaxRequestWorkers, and the server error could disappear. However, it
looks like v1.2.6 actually has better performance than v1.3.1
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)