[
http://jira.codehaus.org/browse/MRM-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=212389#action_212389
]
Steve Pugh edited comment on MRM-1097 at 3/4/10 5:53 AM:
---------------------------------------------------------
We also get this. Our max filehandles is set to the default 1024.
At the time the error was occuring, I did a
ls -l /proc/PROCESSID/fd/
and confirmed there were 1024 filehandles. It also showed that vast majority of
these were sockets.
So then I looked at the outgoing connections for this process using netstat.
I found there were about 800 connections stuck in CLOSE_WAIT state. These were
connections to addresses of the external repositories we have configured in
archiva. Could it be possible that these connections are not not being closed
correctly in certain circumstances?
(Additional info: Our archiva is embedded in tomcat 6.0.16)
was (Author: britsp):
We also get this. Our max filehandles is set to the default 1024.
At the time the error was occuring, I did a
ls -l /proc/PROCESSID/fd/
and confirmed there were 1024 filehandles. It also showed that vast majority of
these were sockets.
So then I looked at the outgoing connections for this process using netstat.
I found there were about 800 connections stuck in CLOSE_WAIT state. These were
connections to addresses of the external repositories we have configured in
archiva. Could it be possible that these connections are not not being closed
correctly in certain circumstances?
> 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.4
>
>
> 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
