Internal Website Search

during a transaction are held in the persistence context by weak references. Therefore, when a managed ... references or soft references instead of weak references . The contains method can check if a specified

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

(which serves as a first level cache). The valid values are " weak " , "soft " and "strong ". Modified

(unlike weak references). support Support Thank you for your investigation.  I ... ; Perhaps setting ObjectDB to use weak references but then using persistent object callback/listeners to track ... holding on to memory when it should be freed? Even after using " weak " references, and closing

are " weak ", "soft" and "strong". Modified entities are always held by strong ... . Question : What exactly is the difference between " weak ", "soft", and "strong" references? dmoshal ... /understanding- weak -references For more information, please see: https://www.google.com/search?q=java+strong+ weak +soft+reference&gws_rd=ssl support Support

Golyshkin ObjectDB allocates internal data structures for every persisted object, but uses weak ... released, please provide a heap dump. support Support Yes we know about WEAK REFERENCEs in ObjectDb

reflection mode (with enhancement, weak references are used more intensively, so Product instances

up the Lazy collection (by getting size() of Collection) is a very weak solution. In case

could use makeTransient but if the L2 cache is using weak references  I should not get OutOfMemory

_es BTC EmbeddedSystems This regression was caused by a change in 2.6.4_04 from strong to weak

that become unreachable (tracked by using weak references). When a process starts it tries to delete

changing the default reference cache configuration from weak to soft or strong. However, notice

. For cache purpose - consider soft references, which are something in the middle between weak

, all if fine, but performances are weak . Xirt xirt Sylvain Agreed. Note that we have nearly 100% coverage

deleted during a transaction are held in the cache by weak references. Therefore, when a persistent

Chaches: So level 2 cache is deactivated. References in level 1 cache is weak and we can observe ... of weak references still grows. One could expect that the could be reused if their referenced objects ... transaction. Objects are read so there they are still referenced by weak refernces. GC can collect

Added optional (experimental) support of using clients with different object model versions. Changed references to new flushed objects from ObjectDB to weak references. Cancelled an exception on cascading removal of an already removed object. Renamed internal Enhancer hidden methods to non

Added support of an option to disable broken reference cleaning in the Doctor ( feature request #2341 ). Added support of cascading delete using JDO ( feature request #2329 ). Added logging for "Failed to read from file" error ( issue #2322 ). Added an option for eager background purge of weak

in new automatic activation of indexes. Fixed a regression bug due to changing references to weak

reflection mode ObjectDB has to keep some strong references to objects, which are weak references when entity classes are enhanced. support Support