Skip to Content.
Sympa Menu

grouper-dev - Re: [grouper-dev] Connection Pooling with JNDISourceAdapter

Subject: Grouper Developers Forum

List archive

Re: [grouper-dev] Connection Pooling with JNDISourceAdapter

Chronological Thread 
  • From: "Michael R. Gettes" <>
  • To:
  • Subject: Re: [grouper-dev] Connection Pooling with JNDISourceAdapter
  • Date: Fri, 10 Aug 2007 14:41:23 -0400

I can see the SSL options as a config setting but I think the pooling should just
be coded and NOT a config option. Or, default it to true and expose it as a config
option if you like. I guess this is my way of asking why anyone would NOT want
connection pooling?


On Aug 10, 2007, at 14:15, Shilen Patel wrote:

I simply added one line of code into the file in the setupEnvironment() method.

environment.put("com.sun.jndi.ldap.connect.pool", "true");

Though it probably makes sense to have the "true" value come from the sources.xml file instead of hard coded in the class. Also, since I'm using SSL, I added the following to my JAVA_OPTS environment variable:

-Dcom.sun.jndi.ldap.connect.pool.protocol="plain ssl"

-- Shilen

Michael R. Gettes wrote:
I have a stupid question - how does one add connection pooling to the JNDISourceAdapter?


On Aug 10, 2007, at 10:47, Shilen Patel wrote:


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

Archive powered by MHonArc 2.6.16.

Top of Page