|Switched to 2.4.1 - Suddenly caching of lazy relations is missing [message #1010960]
||Mon, 18 February 2013 10:01
| R. Oldenburg
Registered: September 2011
we are using EL 2.2 and 2.3.x successfully for the last 2 years now.
Now recently when I tried switching to EL 2.4.1 we encounter some strange behaviour:
We got a complex object/entity hierarchy with several lazy bi-directional mappings that now seem to be newly fetched on every access... (i.e. calling getRelatedObjects().iterator())
Did something important change on the lazy relation handling?
Could it be related to @JoinFetch(JoinFetchType.OUTER) or to our default WEAK shared cache setting?
In EL 2.3 the already fetched relational entities have been perfectly efficient re-used. (SQL-"Fine"-Log was some 2,5MB and now some 58 MB for the same routine. It contains the same SQLs over and over again)
I am totaly out of ideas currently...
Thanks in advance,
Powered by FUDForum
. Page generated in 0.02103 seconds