 75 | ", "soft" and "strong". Modified entities are always held by strong references in the persistence |
19 | it and it is automatically removed from the persistence context. ObjectDB can be configured to use strong references |
19 | required in order to follow this guide, but a strong background and understanding of the Java |
19 | required in order to follow this guide, but a strong background and understanding of the Java |
7 | to have my code called to manipulate the softReferenceData in my JdoBlob2 instances, so there is a strong ... is due to ObjectDB datastore page file cache keeping strong references to the pages that comprise the data ... and you expect to be released? Can you see a path of strong references from a root that holds |
6 | ? Do you always use only enhanced classes? With enhanced classes ObjectDB is not expected to hold strong references ... the heap per type and paths of strong references from roots to objects?
@Entity
class ... with strong references, so hopefully the heap dump could help in understanding the issue. The current |
4 | - but it is less efficient and has some limitations. For example, strong references to your objects ... (unlike makeTransient / makeTransientAll). ObjectDB doesn't hold strong references to hollow objects, so if your application doesn't hold strong references either - they can be garbage collected |
3 | of its result objects already created and reside in memory ? Q2: Do I need to manually use strong ... ). You can either use application managed strong references or you can set the configuration, so strong references ... references, which are something in the middle between weak and strong references. The size of the L1 |
3 | ). 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? The following blog ... For more information, please see: http://www.google.com/search?q=java+strong+weak+soft+reference dmoshal |
2 | a collection after it releases the last strong reference to the containing entity object? Following ... a strong reference to the containing entity - so this unexpected state would be avoided. felixobjectdb |
