[
http://jira.codehaus.org/browse/MRM-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=244416#action_244416
]
Maria Odea Ching commented on MRM-1097:
---------------------------------------
I made some fixes for this in trunk
[-r1039004|http://svn.apache.org/viewvc?revision=1039004&view=revision]. These
are the changes:
* upgrade nexus indexer to 3.0.1 + added logger bean which is needed by
NexusIndexer
* for deployments/proxied artifacts, create and close indexing context when
indexing task is executed as compared to the original behavior where the
indexing context is created before it is queued (so as the indexing task queue
builds up, more indexing contexts are being opened/created which might be
causing the too many open files problem)
* updated unit tests with changes made
> 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
>
> Attachments: MRM-1097.patch
>
>
> 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
