-
1. Re: on-load strategy limitations
triathlon98 Apr 9, 2004 6:28 AM (in response to triathlon98)More info, even the "none" strategy causes a OutOfMemoryException after a while. Even though the code runs in multiple transactions, things go wrong after a while.
What's more the logs also show that one of the fields (which contains the key from a 1-N relationship) gets updated, even though the client code is read-only.
Any ideas about how this can be fixed or workarounds ?
Joachim -
2. Re: on-load strategy limitations
triathlon98 Apr 9, 2004 8:22 AM (in response to triathlon98)I also tried setting <max-capacity>200</max-capacity> in container-cache-conf, but I still get the OutOfMemory (this was with default on-load).
Joachim -
3. Re: on-load strategy limitations
triathlon98 Apr 9, 2004 1:44 PM (in response to triathlon98)As I could not get any of the load strategies to work, and after re-reading the CMP chapter in the manual, I can only conclude that something is wrong with the preload cache. While the manual says the contents is linked with soft references, this does not seem to be the case, as the OutOfMemory seems to happen during this pre-loading.
I also tested whether running this example inside or outside a transaction helps, but it does not seem to make a difference.
Joachim -
4. Re: on-load strategy limitations
triathlon98 Jun 20, 2004 6:39 PM (in response to triathlon98)Seems fixed in 3.2.4
Joachim