If I understand it correctly, then the limit is per user/user group. I run the WIAB server with dedicated user "wave", so I believe that most of those 1024 files were opened per wavelet. Also, I think that the current file based implementation reads all the wavelets into memory on startup.
2011/3/22 Michael MacFadden <[email protected]> > Yuri, > > Two comments. First in java apps on things like JBoss, Tomcat, Jetty, etc, > sometimes it is actually the server that runs into this problem. Meaning > the server is opening file resources, pipes, ports, etc. The problem may > show up in your code if you then open a bunch of files, but the problem > could itself be in the app server. I have seen this on many java apps > running in linux. > > That being said, I don't think WiaB should be opening that many files, even > if there are 65000 wavelets in the system (or 1024 for that matter) WiaB > should not be keeping all of those files open all of the time. We should > check to make sure we aren't just blindly keeping files open like that. I > suspect that we are not. > > As I said, you hit this limit a lot with Java Apps in the first place > running in a linux app server, even if that app doesn't itself open many > files. > > ~Michael > > > On Mar 22, 2011, at 7:18 AM, Yuri Z wrote: > > > Hi > > Today waveinabox.net:9898 server had issue with creating new waves - the > > reason was - too many open files. I was able to increase the limit to > 65000 > > from 1024 following the guide at > > http://posidev.com/blog/2009/06/04/set-ulimit-parameters-on-ubuntu/. > > However, there's a question - can file based persistence handle more than > > 65000 wavelets? > >
