Grouper Developers Forum

[Dave Donnelly <>]

"... subject-api should be its own jar file..."
The Subject CVS project build target 'dist' does create a
subject-{version}.jar file. I would suggest that developers
in Signet and Grouper use that as a means of including
SubjectAPI functionality in their respective projects.

--Dave


Michael R. Gettes wrote:
> Shilen helped me figure out the problem...
>
> While I modified subject-api and put it in the right places... I was
> doing my testing with ldappc.  I had already changed ldappc to include 
> grouper-lib.jar
> and, as it turns out, grouper-lib.jar has subject-api embedded into 
> it.  Shilen
> and I both believe that subject-api should be its own jar file to 
> eliminate
> this kind of confusion.  I am now enjoying substantial performance 
> benefit with
> subject-api and LDAP interactions in LDAPPC and grouper.
>
> shilen is also correct (i am learning!) that 
> com.sun.jndi.ldap.connect.pool
> should be in the code and other variables need to be established at 
> invocation
> in the system environment.
>
> /mrg
>
> On Oct 2, 2007, at 16:33, Michael R. Gettes wrote:
>
> > I replicated this and I am not seeing a benefit.   I have put the 
> > pool.protocol into
> > the setupEnvironment - no difference.  Any thoughts on this?
> >
> > i checked out subject_031.  modified JNDISourceAdapter.  rebuilt with 
> > ant dist - copied
> > the jar file to ldappc and grouper and ran both - watched the logs - 
> > i don't see efficient
> > pooling going on.  i see connection, bind, unbind and drop.  and it 
> > is still slow.
> >
> > pointers appreciated.
> >
> >         environment.put("com.sun.jndi.ldap.connect.pool", "true");
> >         environment.put("com.sun.jndi.ldap.connect.pool.protocol", 
> > "plain ssl");
> >         environment.put("com.sun.jndi.ldap.connect.pool.initsize", 5);
> >
> > /mrg
> >
> > On Oct 2, 2007, at 8:25, 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