[
https://issues.apache.org/jira/browse/SOLR-16628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686706#comment-17686706
]
ASF subversion and git services commented on SOLR-16628:
--------------------------------------------------------
Commit e20fcf857a32c9c2559ba91cfc68f2ebf5ea09e0 in solr's branch
refs/heads/main from Michael Gibney
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=e20fcf857a3 ]
SOLR-16628: Ensure that InputStreams are closed after Xml parsing (#1302)
> Occasional resource leak around XmlConfigFile parsing
> ------------------------------------------------------
>
> Key: SOLR-16628
> URL: https://issues.apache.org/jira/browse/SOLR-16628
> Project: Solr
> Issue Type: Bug
> Affects Versions: 8.9
> Reporter: Michael Gibney
> Priority: Minor
> Time Spent: 8h 20m
> Remaining Estimate: 0h
>
> Currently, xml config file parsing can in exceptional circumstances lead to
> resource leaks (InputStream not being closed). This has occasionally [shown
> up in
> tests|https://issues.apache.org/jira/browse/SOLR-16336?focusedCommentId=17678323#comment-17678323]
> and presumably could also manifest in the wild.
> I suspect (but am not certain) that these changes may have been introduced in
> version 8.9 by SOLR-15337 (closing of byte streams in xml parsing is unusual
> iiuc in that according to spec, closing is handled internal to the parser, so
> it's easy to rely on that behavior and things will usually be ok. But we
> should take extra steps to ensure the InputStreams are always closed).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
