jackrabbit-dev mailing list archives

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

    [ https://issues.apache.org/jira/browse/JCR-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740021#action_12740021
] 

Stefan Guggisberg commented on JCR-2240:
----------------------------------------

> I guess 'never deleted' is not correct. The files are actually deleted, but only at the
discretion of the garbage collection and the finalizer.

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

i assume the tmp files are created by o.a.j.util.TransientFileFactory.  
tmp files will be deleted when their associated marker objects are 
reclaimed by the garbage collector.

> 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
>
> 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.


Mime
View raw message