[
https://issues.jboss.org/browse/MODCLUSTER-536?page=com.atlassian.jira.pl...
]
Wayne Wang commented on MODCLUSTER-536:
---------------------------------------
From the latest load tests where requests were sent through web server
(httpd) and routed to wildfly10.
I only test the performance, and not testing HA singleton and fail-over. This time, I have
NOT seen the outcome of lsof to grow steadily. I tested 14 times, and the servers look
strong.
I re-tested the HA singleton configuration to record each shutdown of wildfly instance,
and I was able to replicate the issue again with only 4 times of load test.
So it looks like the shutdown of wildfly instance (behind web server) is related to the
issue of growing number of open files in both vm for wildfly instance and web server. Is
there any way to get around it other than restart the httpd?
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)