[jira] Updated: (FELIX-2646) [Framework] Locking could be used to prevent concurrent access to a single bundle cache

["Richard S. Hall (JIRA)" <ji...@apache.org>]

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

Richard S. Hall updated FELIX-2646:
-----------------------------------

    Attachment: FELIX-2646.txt

Here is a proposed patch for bundle cache locking. I did a simple test by starting the framework twice from the same directory and it appears to work. The main downside of adding locking is it adds one more open file per framework instance. What do people think, is this a worthy addition?

> [Framework] Locking could be used to prevent concurrent access to a single bundle cache
> ---------------------------------------------------------------------------------------
>
>                 Key: FELIX-2646
>                 URL: https://issues.apache.org/jira/browse/FELIX-2646
>             Project: Felix
>          Issue Type: New Feature
>          Components: Framework
>    Affects Versions: framework-3.0.4
>            Reporter: Richard S. Hall
>            Priority: Minor
>             Fix For: framework-3.2.0
>
>         Attachments: FELIX-2646.txt
>
>
> Currently, the framework completely ignores concurrent access to the same bundle cache and leaves it as a configuration issue. The downside of this approach is that a mistaken configuration could corrupt your bundle cache. We could avoid this by introducing some sort of bundle cache locking protocol using java.nio.channels.FileLock. I think it would be sufficient to simply implement a fail-fast locking protocol.

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