Bug 280778 - Doc: expand on FullIdentityMap usage to avoid memory leaks
Summary: Doc: expand on FullIdentityMap usage to avoid memory leaks
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL: http://wiki.eclipse.org/Introduction_...
Whiteboard:
Keywords:
Depends on: 221002
Blocks:
  Show dependency tree
 
Reported: 2009-06-18 10:34 EDT by Michael OBrien CLA
Modified: 2022-06-09 10:23 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael OBrien CLA 2009-06-18 10:34:37 EDT 
The following elug URL states when to use FullIdentityMap but 

http://wiki.eclipse.org/Introduction_to_Cache_(ELUG)#Guidelines_for_Configuring_the_Cache_and_Identity_Maps

>Memory Leak specifics 

"WARNING: Use the FullIdentityMap only if the class has a small number of finite instances. Otherwise, a memory leak will occur."

>comment 
 We need to relate this potiential memory leak behavior to bugs such as bug# 221002 and "how small" a cache size will cause leakage, 
where subclass leakages will also occur and under what kind of load/time constraints.
Without these specific constraints, the user may avoid use of this superclass.
Comment 1 Michael OBrien CLA 2009-06-18 10:41:47 EDT 
>Any numbers will be based on Object size/complexity and relationship size/type - this will involve simulation work.
Comment 2 Eclipse Webmaster CLA 2022-06-09 10:23:36 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink