[
https://issues.apache.org/jira/browse/SOLR-12386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16488133#comment-16488133
]
Hoss Man commented on SOLR-12386:
---------------------------------
bq. GetResource() may also return null ...
But at least then you can tell the difference between "getResource() returned
null meaning we didn't locate the file resource name" and "openConnection()
threw 'IOException: Too many open files'"
And now that i look at it again: if we used {{Enumeration<URL>
getResources(String name)}} instead of {{URL getResource(String)}} wouldn't
that ensure we would get an IOException instead of "null" in the case you're
talking about where even the lookup of the name failed because of too many
filehandles?
> Test fails for "Can't find resource" for files in the _default configset
> ------------------------------------------------------------------------
>
> Key: SOLR-12386
> URL: https://issues.apache.org/jira/browse/SOLR-12386
> Project: Solr
> Issue Type: Test
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Reporter: David Smiley
> Priority: Minor
> Attachments: cant find resource, stacktrace.txt
>
>
> Some tests, especially ConcurrentCreateRoutedAliasTest, have failed
> sporadically failed with the message "Can't find resource" pertaining to a
> file that is in the default ConfigSet yet mysteriously can't be found. This
> happens when a collection is being created that ultimately fails for this
> reason.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
