[jira] Issue Comment Edited: (FELIX-819) unable to rename / delete bundle cache location on update or uninstall

["Walid Joseph Gedeon (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FELIX-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648976#action_12648976 ] 

wgedeon edited comment on FELIX-819 at 11/19/08 2:51 AM:
---------------------------------------------------------------------

I've renamed the issue to reflect findings.

PS: attached patch does not address issue resolution anymore, should it be deleted? or is there a way to invalidate it?

      was (Author: wgedeon):
    I've renamed the issue to reflect findings
  
> unable to rename / delete bundle cache location on update or uninstall
> ----------------------------------------------------------------------
>
>                 Key: FELIX-819
>                 URL: https://issues.apache.org/jira/browse/FELIX-819
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework
>    Affects Versions: felix-1.4.1
>         Environment: Windows (XP Pro)
>            Reporter: Walid Joseph Gedeon
>         Attachments: org.apache.felix.framework (BundleArchive).patch, test-bundles.zip
>
>
> Hello all,
> It looks like the revision.location is missing from the bundle cache after the shutdown purge. Steps:
> - install bundle
> - update bundle
> - shutdown
> The next start shows a:
> ERROR: org.apache.felix.framework.cache.BundleCache: Error creating archive. (java.io.FileNotFoundException: .\felixcache\bundle24\version2.0\revision.location (The system cannot find the file specified))
> Looking in the directory, the file is not there.
> Stepping through the code shows that the BundleArchive.purge() attempts to rename the last bundle revision to a fresh one... except that the File.rename is not platform independent (it fails on windows quite often).
> When BundleCache.getSecureAction().renameFile(revisionDir, currentDir) returns false (rename failed), createRevisionFromLocation follows and does not include a new revision.location file.
> Maybe a call to setRevisionLocation() is to be made after createRevisionFromLocation (BundleArchive:866)? I'll try that out...

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