Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EclipseLink » MultiTenant cache headache
MultiTenant cache headache [message #1063953] Sun, 16 June 2013 15:49
Thomas Kratz is currently offline Thomas KratzFriend
Messages: 163
Registered: July 2009
Senior Member
Hi, I got somewhat further with my explorations of the MultiTenant features. I found the with the default settings the L2 Cache is practically disabled.

So here goes my question (I have no clue about the inner workings of the cache). Will I be safe to use tenants-share-cache when I use distinct Id s across all tenants? Or will I get query caching issues when I use (as intended) schema per tenant and have the same query running against different tenants (for e.g. select all from xzy).

I found some issues with my explorations of tenants-share-cache, when I try to lazy load after transaction-commit, em-closed. With tenants-share-cache set to true those attempts fail with the session complaining that the tenant-id properties has not been set (which has been set on the em). If this is intented behaviour, I would like to understand it, otherwise I suppose I provide a testcase and a ticket.

Regards
Thomas
Previous Topic:Composite Primary key Sequence in JPA EclipseLink DynamicPersistence
Next Topic:ClassLoader problem using JPA with Native Eclipselink project file
Goto Forum:
  


Current Time: Sat Dec 20 15:22:27 GMT 2014

Powered by FUDForum. Page generated in 0.01515 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software