Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
None
-
None
Description
There are warn messages about 'overwriting cached item' in the logs when an application shares a JCR session for reads. So far, this usage is considered OK, while sharing a session for writes is discouraged. Jackrabbit should not log warnings for usages we consider valid.
AFAICS repository consistency is not at risk here. There's no guarantee or requirement that only one Item instance is around for a given ItemId. The important piece is the underlying ItemState, which is managed by the SharedItemStateManager with a diffferent synchronization/locking implementation.