You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2010/05/08 06:00:48 UTC

[jira] Closed: (INFRA-2660) Need to increase file handle limits on Hudson Ubuntu servers

     [ https://issues.apache.org/jira/browse/INFRA-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gavin closed INFRA-2660.
------------------------

    Resolution: Fixed

done

> Need to increase file handle limits on Hudson Ubuntu servers
> ------------------------------------------------------------
>
>                 Key: INFRA-2660
>                 URL: https://issues.apache.org/jira/browse/INFRA-2660
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Hudson
>            Reporter: Donald Woods
>            Priority: Critical
>
> When running our OpenJPA 1.3.x project on Ubuntu (minerva but vesta has the same issue) the build fails during our unit tests due to insufficient file handles -
> Caused by: java.io.FileNotFoundException: /home/hudson/hudson-slave/workspace/OpenJPA-13x/1.3.x/openjpa-persistence-jdbc/target/test-classes/org/apache/openjpa/persistence/proxy/entities/RiderType.class (Too many open files)
> 	at java.io.FileInputStream.open(Native Method)
> 	at java.io.FileInputStream.<init>(FileInputStream.java:106)
> 	at org.apache.openjpa.lib.util.J2DoPrivHelper$29.run(J2DoPrivHelper.java:648)
> 	at java.security.AccessController.doPrivileged(Native Method)
> 	at org.apache.openjpa.lib.meta.ClassArgParser.getFromClassFile(ClassArgParser.java:303)
> 	at org.apache.openjpa.lib.meta.ClassArgParser.parseTypeNames(ClassArgParser.java:214)
> 	... 70 more
> Can someone with root level sudo increase the defaults to something higher than 1024?
> Edit the /etc/security/limits.conf file. At the end of the file just above "# End of File" enter the following values:
> *	soft	nofile	65535
> *	hard nofile	65535
> Then type 'ulimit -n' and if it returns 1024 instead of the above, then add the following to /etc/pam.d/common-session:
> session required pam_limits.so

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.