[OPENJPA-2285] L2 cache doesn't store FK(s) back into the cache when lazy loading data.

• Type: Bug
• Status: Reopened
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.0.1, 2.1.1, 2.2.0, 2.3.0, 2.4.0
• Component/s: datacache, performance
• Assignee: Richard G. Curtis
• Reporter: Richard G. Curtis
• Created: 25/Oct/12 19:09
• Updated: 05/Apr/15 16:16

Description

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.

Issue Links

• is duplicated by: OPENJPA-2524 Lazy fields are not updated in L2 cache.