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.
|Status||Open [ 1 ]||Closed [ 6 ]|
|Assignee||Richard S. Hall [ rickhall ]|
|Fix Version/s||framework-3.0.6 [ 12315494 ]|
|Fix Version/s||framework-3.2.0 [ 12315053 ]|
|Resolution||Fixed [ 1 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|25d 23h 55m||1||Richard S. Hall||03/Nov/10 20:41|