[Carbon-jira] [jira] Created: (WSAS-829) application server going down: too many open files

[Joost de Jonge (JIRA)]

application server going down: too many open files
--------------------------------------------------

                 Key: WSAS-829
                 URL: https://wso2.org/jira/browse/WSAS-829
             Project: WSO2 WSAS
          Issue Type: Bug
         Environment: Ubuntu 10.04 LTS ( the Lucid Lynx ) and wso2as-4.1.0

            Reporter: Joost de Jonge
            Assignee: Afkham Azeez
            Priority: High


My test client (isolated from a much larger set of regression sets) did properly run on wso2appserver 4.0.0 but fails on wso2as-4.1.0.

It seems that sockets are not closed properly.

INFO   | jvm 1    | 2011/09/23 10:22:33 | [2011-09-23 10:22:33,267] ERROR {org.apache.tomcat.util.net.NioEndpoint} -  Socket accept failed
INFO   | jvm 1    | 2011/09/23 10:22:33 | java.io.IOException: Too many open files
INFO   | jvm 1    | 2011/09/23 10:22:33 |   at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
INFO   | jvm 1    | 2011/09/23 10:22:33 |   at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:152)
INFO   | jvm 1    | 2011/09/23 10:22:33 |   at org.apache.tomcat.util.net.NioEndpoint$Acceptor.run(NioEndpoint.java:770)
INFO   | jvm 1    | 2011/09/23 10:22:33 |   at java.lang.Thread.run(Thread.java:662)

The test client itself is recently changed and generated by WSDL2Java from wso2as-4.1.0, so I first suspected my modifications and/or the new WSDL2Java.

Yesterday however I decided to run the same client ( no modifications, no recompilation) against the older wso2appserver 4.0.0 and that went perfect again.

Although my client basically tests heavy multithreaded use of different server resources it turns out that even a single thread shows the problem.
This single thread is creating a single serverStub and then calls the same server method in a loop. It seems that the problem arises after some 600-700 calls.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira