[
http://jira.codehaus.org/browse/MRM-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168569#action_168569
]
Lou S commented on MRM-1097:
----------------------------
Can you elaborate on the OS fix? We have the same issue but what we did was
crank up our FDs to 65K and it has seemed to gone away presumably because it
gives Archiva more space to breath. We also changed the Apache socket timeout
in front of our Archiva servers from 0 (never) to 30 minutes. The former seems
a bit much considering the default is 1024 on RHEL. Thoughts?
> Error 500 "too many open files"
> -------------------------------
>
> Key: MRM-1097
> URL: http://jira.codehaus.org/browse/MRM-1097
> Project: Archiva
> Issue Type: Bug
> Components: system
> Affects Versions: 1.1.3
> Environment: Linux RedHat, Tomcat 6 + Native Connector
> Reporter: Marc Lustig
> Fix For: 1.2-M2
>
>
> In our start-script we have configured "ulimit -n 10000"
> But still, occassionally we get http error 500 "java.io.FileNotFoundException
> ... (Too many open files)" on a Maven-artifact-request.
> I suppose the files are not properly closed after they are delivered.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
