Bug 124391 (DEFECT000315258)

Summary: Disconnect behavior is wrong
Product: [Novell Products] NDS SDK Reporter: Steve Sonntag <vtag>
Component: LDAP Java SDKAssignee: Jeff Vincent <jvincent>
Status: VERIFIED FIXED QA Contact: Sundar Swamy <ssundar>
Severity: Normal    
Priority: P5 - None CC: aclark
Version: OCT 2006 NDKKeywords: English
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

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


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

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

---------
<remedy_version_found_in> February NDK </remedy_version_found_in>
---------
<remedy_milestone> BLANK </remedy_milestone>
---------
<remedy_details> Disconnect reconnects - it should reconnect only if
      the app calls bind. </remedy_details>
---------
<remedy_notes> vtag (  12/11/2002 11:21:59 AM  Testing -  ) Disconnect
      has been fixed.

The behavior of disconnect for a clone has also been fixed.
If a clone disconnects, it is disassociated with the existing
connection and issued a new connection.  Previously the
new connection was completly different, but now the new
connection has the same host, port, socket factory, protocol
version as the original connection.

-Steve

 </remedy_notes>