jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-2240) Binary value may leave temp file behind
Date Thu, 06 Aug 2009 12:56:14 GMT

     [ https://issues.apache.org/jira/browse/JCR-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Marcel Reutegger updated JCR-2240:

    Priority: Minor  (was: Major)

> in which case i wouldn't qualify this issue as 'major bug' but rather as an improvement.

agreed on the priority, but I still think this is a bug, because dispose is explicitly and
I would expect that it frees resources that the Binary instance holds.

Anyway, the required changes to fix this bug are already present in the patch for JCR-2238.
I suggest we keep this issue open until JCR-2238 is fixed and then set it to fixed as well.

> Binary value may leave temp file behind
> ---------------------------------------
>                 Key: JCR-2240
>                 URL: https://issues.apache.org/jira/browse/JCR-2240
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>            Reporter: Marcel Reutegger
>            Priority: Minor
> The following call leaves a temp file behind that is never deleted:
> InputStream in = ...
> ValueFactory vf = ....
> vf.createBinary(in).dispose();
> Only happens when the datastore is disabled.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message