[
https://issues.apache.org/jira/browse/SOLR-12386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16488172#comment-16488172
]
Hoss Man commented on SOLR-12386:
---------------------------------
BTW...
{quote}IMHO, the file handle leak in the mentioned commit could habe been fixed
by just using try-with-resources around Class(Loader)#getResourceAsStream() ...
{quote}
...that would have solved that particular leak, but it would not have fixed the
error message returned in the event that the {{getResourceAsStream()}} _in that
line of code_ returned 'null' down the road because some _other_ place in the
code had a different resource leak ... we would still have the possibility of
the caller throwing confusing {{invalid API spec:
apispec/core.config.Commands.json}} exceptions because the method just returned
'null' and it couldn't distinguish "resource doesn't exist" from "OS wouldn't
let the JVM open that resource"
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
