ElementCollection Cannot Be Put To Cache When Lazy Loading Is Used
(Doc ID 1453931.1)
Last updated on MARCH 04, 2019
Applies to:Oracle TopLink - Version 188.8.131.52.0 to 184.108.40.206.0 [Release Oracle11g]
Information in this document applies to any platform.
While using Toplink Grid with Grid Cache configuration, when ElementCollection is configured to use lazy loading, it is always fetched from database by EclipseLink and not
put to cache when the object is read repeatedly.
TopLink 220.127.116.11.0 that comes with WebLogic 10.3.4
Issue occurs with TopLink 18.104.22.168.0 Coherence 22.214.171.124 and Coherence 3.5.3
STACK TRACE / RELEVANT THREAD DUMP INFORMATION:
Following output generated while running the "java test.Test" multiple times, however for the first time I see two SQL's
[EL Fine]: Connection(20415955)--SELECT SHIP_ID, SHP_DESCRIP, VERSION FROM SR_SHIPMENT WHERE (SHIP_ID = ?) bind => 
[EL Fine]: Coherence(Shipment)::Get: 1 result: null
[EL Fine]: Connection(20415955)--SELECT t0.CGO_NATURE FROM SR_SHIPMENT_CARGNAT t0 WHERE (t0.SHIP_ID = ?) bind => 
during the second/third iteration can see only the following SQL
[EL Fine]: Connection(23438274)--SELECT t0.CGO_NATURE FROM SR_SHIPMENT_CARGNAT t0 WHERE (t0.SHIP_ID = ?) bind => 
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|STACK TRACE / RELEVANT THREAD DUMP INFORMATION:|