[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-536) List of open files grows steadily during load test through mod_cluster

[Wayne Wang (JIRA)]

    [ https://issues.jboss.org/browse/MODCLUSTER-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13287017#comment-13287017 ] 

Wayne Wang commented on MODCLUSTER-536:
---------------------------------------

I found the server produced error and the lsof showed over 3000, so I set the soft limit to 4096 and hard limit on 8192. However, this issue persisted.

for example, for the machine starting up httpd, 

daemon soft nofile 4096
daemon hard nofile 8192

Note, the machine that starting up httpd will spawn httpd processes under user daemon.

> 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)