32 | Entity Management Settings: <entities> <enhancement agent="true" reflection="warning" /> <cache ref="weak" level2="0mb ... <cache ref="weak" level2="0mb" /> The <cache> element specifies settings of the two cache ... are "weak", "soft" and "strong". Modified entities are always held by strong references in |
26 | Working with JPA Entity Objects during a transaction are held in the persistence context by weak references. Therefore, when a managed entity ... soft references instead of weak references. The contains method can check if a specified entity object |
20 | Entity Management Config questions/setting/entities: <cache ref="weak" level2="0mb" /> The <cache> element specifies settings ... ). The valid values are "weak", "soft" and "strong". Modified entities are always held by strong ... : What exactly is the difference between "weak", "soft", and "strong" references? dmoshal David Moshal |
18 | Is ObjectDB a NoSQL Database?ObjectDB is a unique NoSQL database. It doesn't have the known disadvantages and limitations of NoSQL technology, which are weak query capabilities and lack of ACID (atomicity, consistency, isolation, durability). Unlike other NoSQL solutions, ObjectDB provides full support of rich complex queries |
18 | Soft Reference Object Cache Recommendation because this is the way soft references work (unlike weak references). support Support Thank ... suggestions? Perhaps setting ObjectDB to use weak references but then using persistent object ... ObjectDB is not holding on to memory when it should be freed? Even after using "weak" references |
13 | Memory Leaks after COMMIT operation (checked on versions 2.6.5 & 2.6.6.b01) for every persisted object, but uses weak references, so as soon as you release your own references ... ObjectDB objects are not released, please provide a heap dump. support Support Yes we know about WEAK |
13 | significant performance decrease agent="true" reflection="warning" /> <cache ref="weak" level2="4096mb" /> <persist serialization ... " /> ... <cache ref="weak" level2="4096mb" /> hgzwicker Hans-Georg Zwicker Larger cache can help, but not |
7 | Best practise loading big data: <cache ref="weak" level2="0" /> So level 2 cache is deactivated. References in level 1 cache is weak ... size and the number of weak references still grows. One could expect that the could be reused ... just one open transaction. Objects are read so there they are still referenced by weak refernces. GC |
4 | Use temporary files to enable very large transactions entity objects. <cache ref="weak" level2="0" /> When the 2nd level cache is enabled, ObjectDB ... > <enhancement agent="false" reflection="ignore" /> <cache ref="weak" level2="0 ... () are weak references and can be removed by GC. Can you explain this case? btc_es BTC EmbeddedSystems |
1 | [ODB1] Chapter 6 - Persistent Objects been modified or deleted during a transaction are held in the cache by weak references |
