potential memory in jldap if not used carefully

["james liang" <blueyonder@excite.com>]

Thought I share this with others that use JLDAP.  

I found that if you use JLDAP's async search mechanism and you don't fetch everything, you need to call LDAPConnection.abandon() on it.  Otherwise, the LDAPSearchQueue will stay around (even if "your" code doesn't a hold any reference to it).  The leak is about 1504 byte per search.

-James

_______________________________________________
Express Yourself - Share Your Mood in Emails!
Visit www.SmileyCentral.com - the happiest place on the Web.