Bug 124352 (DEFECT000281091)

Summary: Memory Hog in Novell LDAP jdk.
Product: [Novell Products] NDS SDK Reporter: atul mahajan <atul.mahajan>
Component: LDAP Java SDKAssignee: atul mahajan <atul.mahajan>
Status: RESOLVED FIXED QA Contact: Sundar Swamy <ssundar>
Severity: Blocker    
Priority: P5 - None CC: aclark, atul.mahajan
Version: OCT 2006 NDKKeywords: English
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Third Party Developer/Partner Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Rajkumar V 2005-10-10 22:54:38 UTC 


------- Bug moved to this database by vrajkumar@novell.com 2005-10-10 16:54 -------

This bug previously known as bug DEFECT000281091 at remedy/
remedy/show_bug.cgi?id=DEFECT000281091
Originally filed under the NDS SDK product and LDAP Java SDK component.

---------
<remedy_version_found_in> BLANK </remedy_version_found_in>
---------
<remedy_milestone> BLANK </remedy_milestone>
---------
<remedy_details> We are using ldap jdk on our ichain box to get to NDS
      using jvm 1.3 on netware 5.1 sp2.
Under a moderate stress of about 200 requests/s I see the heap keeps on
growing irrespective of the max heap settings. It also kicks in the garbage
Collector very frequently.
Eventually it runs out of memory.
We identified by taking the jvm heap dump that for some reasons a large number
of ldap objects were residing in the memory. I can send the concerned heap
dumps taken as well.
The application program which receives 200 reqs/s using ldap libraries does
connection pooling of the ldap connections(of about 15-20).
Cameron Morris was also able to reproduce and identify this.
 </remedy_details>
---------
<remedy_notes> cmorris (  10/2/01 11:07:14 AM  Fixing - Fix Is Checked-In
      ) See the "Developer info" tab

 </remedy_notes>