You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2013/05/16 11:41:16 UTC
[jira] [Resolved] (JCR-3596) Reduce level for 'overwriting cached
item' log messages in ItemManager
[ https://issues.apache.org/jira/browse/JCR-3596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger resolved JCR-3596.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.7.1
2.6.2
Assignee: Marcel Reutegger
Fixed in trunk in http://svn.apache.org/r1483276
and merged into 2.6 branch in http://svn.apache.org/r1483277
> Reduce level for 'overwriting cached item' log messages in ItemManager
> ----------------------------------------------------------------------
>
> Key: JCR-3596
> URL: https://issues.apache.org/jira/browse/JCR-3596
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Minor
> Fix For: 2.6.2, 2.7.1
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira