You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Richard S. Hall (JIRA)" <ji...@apache.org> on 2008/11/17 20:03:44 UTC

[jira] Commented: (FELIX-819) revision.location missing on update

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

Richard S. Hall commented on FELIX-819:
---------------------------------------

I wonder why there would be a failure in renaming. Typically under Windows failures occur because the file is open, but the revision.location file should not remain open. Do you have any ideas about why it is failing? Thanks for the feedback.

> revision.location missing on update
> -----------------------------------
>
>                 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
>
>
> 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.