lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (LUCENE-6608) Potential resource leak in
Date Thu, 25 Jun 2015 19:37:04 GMT


ASF GitHub Bot commented on LUCENE-6608:

GitHub user rmp91 opened a pull request:

    LUCENE-6608: solved potential resource leakage

You can merge this pull request into a Git repository by running:

    $ git pull LUCENE-6608

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #161
commit 2f9abc607d083a3e1dee95b3d715ffce05839415
Author: Rishabh Patel <>
Date:   2015-06-25T19:32:59Z

    solved potential resource leakage


> Potential resource leak in
> ------------------------------------------------
>                 Key: LUCENE-6608
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: modules/analysis
>    Affects Versions: Trunk
>            Reporter: Rishabh Patel
>            Priority: Minor
>              Labels: github-import
> The input and output object streams are being closed in the try block. These resources
will not be closed if an exception occurs in the try block
> We can use the finally block to explicitly close these resources or use the new try-with-resources
construct where they are implicitly closed.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message