Grouper Developers Forum

[Tom Barton <>]

This works for Sun's JVM, and it is easy for a site to make this simple 
change if that's what they're running. What vendor-independent 
connection pooling approaches are available?

Shilen Patel wrote:
> Hi Michael,
>
> I added the following line of code in the setupEnvironment() method of 
> the JNDISourceAdapter class.
>
> environment.put("com.sun.jndi.ldap.connect.pool", "true");
>
>
> Then since I'm using SSL, I added the following to the java command line.
>
> -Dcom.sun.jndi.ldap.connect.pool.protocol="plain ssl"
>
>
>
> -- Shilen
>
>
> Michael R. Gettes wrote:
> > Shilen,
> >
> > How did you enable connection pooling?  Did you do something 
> > equivalent to
> > adding -Dcom.sun.jndi.ldap.connect.pool="true" to the java 
> > commandline?  Or something
> > else?
> >
> > /mrg
> >
> > On Aug 10, 2007, at 10:47, Shilen Patel wrote:
> >
> > > Hello,
> > >
> > > I recall the connection pooling issue with the JNDISourceAdapter 
> > > being brought up before, but I don't see any Jira issues on that.  So 
> > > I thought I would share some results.  Simply by adding connection 
> > > pooling to the JNDISourceAdapter, I'm seeing a significant 
> > > performance improvement while making repeated calls to 
> > > Member.getSubject().  For instance, for a group with 120 members, 
> > > retrieving the Subject objects for all 120 members resulted in a 60% 
> > > performance improvement while using connection pooling.
> > >
> > > -- Shilen