You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Stefan Guggisberg (JIRA)" <ji...@apache.org> on 2010/11/17 17:33:13 UTC

[jira] Created: (JCR-2813) "overwriting cached entry" warnings

"overwriting cached entry" warnings
-----------------------------------

                 Key: JCR-2813
                 URL: https://issues.apache.org/jira/browse/JCR-2813
             Project: Jackrabbit Content Repository
          Issue Type: Bug
            Reporter: Stefan Guggisberg
            Priority: Critical


when using multiple concurrent sessions you'll find *lots* of log entries like:

    03.11.2010 21:17:03 *WARN * ItemStateReferenceCache: overwriting cached entry ad79ca57-5eb1-4b7d-a439-a9fd73cc8c5a (ItemStateReferenceCache.java, line 176)

those are actually legitimate warnings since there's a siginificant risk of data loss/inconsistency involved.

this is apparently a regression of changes introduced by JCR-2699, specifically svn r1004223

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


[jira] Commented: (JCR-2813) "overwriting cached entry" warnings

Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/JCR-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935358#action_12935358 ] 

Stefan Guggisberg commented on JCR-2813:
----------------------------------------

> In revision 1038201 I added a mechanism that avoids the big synchronization block but still makes sure that no two threads can concurrently load the same item.

excellent, thanks!

> "overwriting cached entry" warnings
> -----------------------------------
>
>                 Key: JCR-2813
>                 URL: https://issues.apache.org/jira/browse/JCR-2813
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>            Reporter: Stefan Guggisberg
>            Priority: Critical
>             Fix For: 2.0.4, 2.1.3, 2.2.0
>
>
> when using multiple concurrent sessions you'll find *lots* of log entries like:
>     03.11.2010 21:17:03 *WARN * ItemStateReferenceCache: overwriting cached entry ad79ca57-5eb1-4b7d-a439-a9fd73cc8c5a (ItemStateReferenceCache.java, line 176)
> those are actually legitimate warnings since there's a siginificant risk of data loss/inconsistency involved.
> this is apparently a regression of changes introduced by JCR-2699, specifically svn r1004223

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


[jira] Resolved: (JCR-2813) "overwriting cached entry" warnings

Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Guggisberg resolved JCR-2813.
------------------------------------

    Resolution: Fixed

partially reverted changes of svn r1004223, 

New Revision: 1036117

> "overwriting cached entry" warnings
> -----------------------------------
>
>                 Key: JCR-2813
>                 URL: https://issues.apache.org/jira/browse/JCR-2813
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>            Reporter: Stefan Guggisberg
>            Priority: Critical
>
> when using multiple concurrent sessions you'll find *lots* of log entries like:
>     03.11.2010 21:17:03 *WARN * ItemStateReferenceCache: overwriting cached entry ad79ca57-5eb1-4b7d-a439-a9fd73cc8c5a (ItemStateReferenceCache.java, line 176)
> those are actually legitimate warnings since there's a siginificant risk of data loss/inconsistency involved.
> this is apparently a regression of changes introduced by JCR-2699, specifically svn r1004223

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


[jira] Updated: (JCR-2813) "overwriting cached entry" warnings

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-2813:
-------------------------------

    Fix Version/s: 2.1.3

Merged to the 2.1 branch in revision 1038599.

> "overwriting cached entry" warnings
> -----------------------------------
>
>                 Key: JCR-2813
>                 URL: https://issues.apache.org/jira/browse/JCR-2813
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>            Reporter: Stefan Guggisberg
>            Priority: Critical
>             Fix For: 2.1.3, 2.2.0
>
>
> when using multiple concurrent sessions you'll find *lots* of log entries like:
>     03.11.2010 21:17:03 *WARN * ItemStateReferenceCache: overwriting cached entry ad79ca57-5eb1-4b7d-a439-a9fd73cc8c5a (ItemStateReferenceCache.java, line 176)
> those are actually legitimate warnings since there's a siginificant risk of data loss/inconsistency involved.
> this is apparently a regression of changes introduced by JCR-2699, specifically svn r1004223

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


[jira] Updated: (JCR-2813) "overwriting cached entry" warnings

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-2813:
-------------------------------

    Fix Version/s: 2.0.4

... and merged to the 2.0 branch in revision 1038609.

> "overwriting cached entry" warnings
> -----------------------------------
>
>                 Key: JCR-2813
>                 URL: https://issues.apache.org/jira/browse/JCR-2813
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>            Reporter: Stefan Guggisberg
>            Priority: Critical
>             Fix For: 2.0.4, 2.1.3, 2.2.0
>
>
> when using multiple concurrent sessions you'll find *lots* of log entries like:
>     03.11.2010 21:17:03 *WARN * ItemStateReferenceCache: overwriting cached entry ad79ca57-5eb1-4b7d-a439-a9fd73cc8c5a (ItemStateReferenceCache.java, line 176)
> those are actually legitimate warnings since there's a siginificant risk of data loss/inconsistency involved.
> this is apparently a regression of changes introduced by JCR-2699, specifically svn r1004223

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


[jira] Updated: (JCR-2813) "overwriting cached entry" warnings

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-2813:
-------------------------------

      Component/s: jackrabbit-core
    Fix Version/s: 2.2.0

In revision 1038201 I added a mechanism that avoids the big synchronization block but still makes sure that no two threads can concurrently load the same item.

> "overwriting cached entry" warnings
> -----------------------------------
>
>                 Key: JCR-2813
>                 URL: https://issues.apache.org/jira/browse/JCR-2813
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-core
>            Reporter: Stefan Guggisberg
>            Priority: Critical
>             Fix For: 2.2.0
>
>
> when using multiple concurrent sessions you'll find *lots* of log entries like:
>     03.11.2010 21:17:03 *WARN * ItemStateReferenceCache: overwriting cached entry ad79ca57-5eb1-4b7d-a439-a9fd73cc8c5a (ItemStateReferenceCache.java, line 176)
> those are actually legitimate warnings since there's a siginificant risk of data loss/inconsistency involved.
> this is apparently a regression of changes introduced by JCR-2699, specifically svn r1004223

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