|MultiTenant cache headache [message #1063953]
||Sun, 16 June 2013 11:49
| Thomas Kratz
Registered: July 2009
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.
Powered by FUDForum
. Page generated in 0.01439 seconds