File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes EJB and other Java EE Technologies and the fly likes Needed: Alternative to JNDI to connect to LDAP Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Soft Skills this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Needed: Alternative to JNDI to connect to LDAP" Watch "Needed: Alternative to JNDI to connect to LDAP" New topic
Author

Needed: Alternative to JNDI to connect to LDAP

Bryan Hughes
Greenhorn

Joined: Feb 16, 2004
Posts: 10
I am currently using JNDI to connect and interact with Sun's LDAP server. However, during performance testing, we've noticed that as the number of user records increase, the speed in which results are returned from the LDAP dramatically decreases.
At this point, after reading about latency issues with JNDI, I'm looking for alternatives. Can someone please comment on their experience with other products that have worked? I'm open to almost anything (openLDAP, Novelle, etc...), so all feedback is appreciated.
Tonny Tssagovic
Ranch Hand

Joined: Dec 30, 2003
Posts: 226
Originally posted by Bryan Hughes:
after reading about latency issues with JNDI.

Why don't u cache the JNDI Lookups with something like a service locator?
Bryan Hughes
Greenhorn

Joined: Feb 16, 2004
Posts: 10
Why don't u cache the JNDI Lookups with something like a service locator?
Can you direct me to some examples of what you're describing? Some of this is new territory for me.
Kishore Dandu
Ranch Hand

Joined: Jul 10, 2001
Posts: 1934
For service locator pattern details(and other J2EE patterns) refer to
"Core J2EE Patterns" from Sun(by Deepak Alur etc)
Dan.


Kishore
SCJP, blog
Kyle Brown
author
Ranch Hand

Joined: Aug 10, 2001
Posts: 3892
    
    5
Are you certain you're not overloading your LDAP server? We've often seen that the bottleneck is there rather than in JNDI. Watch the CPU utilization numbers on your LDAP server to be sure...
Kyle


Kyle Brown, Author of Persistence in the Enterprise and Enterprise Java Programming with IBM Websphere, 2nd Edition
See my homepage at http://www.kyle-brown.com/ for other WebSphere information.
Tonny Tssagovic
Ranch Hand

Joined: Dec 30, 2003
Posts: 226
Originally posted by Bryan Hughes:
Can you direct me to some examples of what you're describing? Some of this is new territory for me.

You can check out the j2ee patterns at Service Locator and I recommend you to download EJB design patterns (free from The server side) You need to register however, and the book is a good read even if you are not using EJBs. (Just skim though it and check the EJB factory pattern which is an EJB specific implementation of the service locator,
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Needed: Alternative to JNDI to connect to LDAP