the easier would be to ping infra (#asfinfra on freenode) and ask them which processes/files are not closed. With a thread stack we should identify them easily. Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau
2013/12/6 Thiago Veronezi <[email protected]>: > It turns out it was not the problem. The build is still behaving. > Do you guys see any other suspect? > > []s, > Thiago. > > > On Fri, Dec 6, 2013 at 5:20 AM, Thiago Veronezi <[email protected]> wrote: > >> I have a feeling that this is caused by this commit. >> http://ci.apache.org/builders/tomee-trunk-ubuntu/builds/763 >> I will add the old checkstyle.xml file and profile back. >> >> []s, >> Thiago. >> >> >> >> On Fri, Dec 6, 2013 at 4:16 AM, AndyG <[email protected]>wrote: >> >>> Seeing this on the buildbot: >>> >>> java.io.IOException: error=24, Too many open files >>> >>> Which is easily resolved with something like ulimit -n 50000 >>> >>> However, this is usually a good indication that 'a' process is leaking >>> file >>> handles. Has anyone done work on files or sockets recently (a socket is >>> often backed by a file on Linux)? >>> >>> For example, not closing sockets is often a cause of this. >>> >>> Andy. >>> >>> >>> >>> -- >>> View this message in context: >>> http://openejb.979440.n4.nabble.com/Buildbot-Too-many-open-files-tp4666569.html >>> Sent from the OpenEJB Dev mailing list archive at Nabble.com. >>> >> >>
