felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard S. Hall (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-2646) [Framework] Locking could be used to prevent concurrent access to a single bundle cache
Date Thu, 28 Oct 2010 13:14:20 GMT

    [ https://issues.apache.org/jira/browse/FELIX-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925795#action_12925795

Richard S. Hall commented on FELIX-2646:

I suppose if it ends up posing such an issue, we could always make it configurable so that
portion of code need not be executed in a 1.3 environment. But I'd rather not make it configurable
in advance to avoid unnecessary configuration options.

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

View raw message