openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Curtis (JIRA)" <>
Subject [jira] [Reopened] (OPENJPA-2285) L2 cache doesn't store FK(s) back into the cache when lazy loading data.
Date Tue, 05 Mar 2013 14:53:12 GMT


Rick Curtis reopened OPENJPA-2285:

An internal test regression was attributed to the change in this JIRA. The problem is that
when CacheStoreMode.USE (default) is set, data should NOT be stored back into the cache. I'll
update the JIRA with more details soon here.
> L2 cache doesn't store FK(s) back into the cache when lazy loading data.
> ------------------------------------------------------------------------
>                 Key: OPENJPA-2285
>                 URL:
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: datacache, performance
>    Affects Versions: 2.0.1, 2.1.1, 2.2.0, 2.3.0
>            Reporter: Rick Curtis
>            Assignee: Rick Curtis
>             Fix For: 2.3.0, 2.2.2
> I ran into a performance bug recently where we aren't caching data, but we could be.
The data that we aren't caching is when lazy loading an unowned relationship .
> For instance, if we have the model Person <-> Address(LAZY, owner) and we find
Person, that data will get stored in the cache. Since Address owns the relationship, we don't
have the FK to cache(yet). Later we go to lazily load the address and we need to issue a joined
query to find the Address which corresponds to our Person. Once that data has been loaded,
we don't store the FK back into the cache.
> With this JIRA I'm going to introduce a change that will make our runtime re-cache the
Person data when additional data is loaded.

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:

View raw message