Grouper Users - Open Discussion List

[Chris Hyzer <>]

Im looking in the source, and I think you need to specify the vt ldap properties file in the sources.xml…

 

 

    <init-param>

      <param-name> ldapProperties_file</param-name>

      <param-value>ldap.properties</param-value>

    </init-param>

 

 

But if you do this it seems you need to move all your connection settings and user/pass etc into the ldap.properties.  Can you try it and let us know?

If wiki updates would help and you have suggestions let me know and I can incorporate your suggestions

 

Thanks,

Chris

 

 

 

From: Hans Westerbeek [mailto:]
Sent: Tuesday, June 30, 2015 4:15 AM
To: Internet2/grouper
Cc: Chris Hyzer
Subject: Re: [grouper] Grouper 2.1.5 loses track of ldap connection (#43)

 

It seems that my organization is using a obsolete(?) way of configuring sources. See [https://github.com/OpenConext/OpenConext-deploy/blob/develop/roles/grouper/templates/sources.xml.j2], it's using the GrouperJndiSourceAdapter.

From the grouper documentation, it is not clear for me how to proceed.

Right now, it seems that grouper is ignoring my connection pool settings (it is initializing the pool at 3 connections even if I have set it to 5). See [https://github.com/OpenConext/OpenConext-deploy/blob/develop/roles/grouper/templates/ldap.properties.j2]

Here's some logging to illustrate my point:

2015-06-30 09:48:10,048: [main] DEBUG AbstractLdapPool.initialize(109) -  - beginning pool initialization

2015-06-30 09:48:10,052: [main] DEBUG AbstractLdapPool.initialize(117) -  - prune pool task scheduled

2015-06-30 09:48:10,053: [main] DEBUG AbstractLdapPool.initialize(125) -  - validate pool task scheduled

2015-06-30 09:48:10,053: [main] DEBUG AbstractLdapPool.initializePool(145) -  - checking ldap pool size >= 3

2015-06-30 09:48:10,078: [main] DEBUG AbstractLdapPool.initialize(131) -  - pool initialized to size 3

2015-06-30 09:48:10,083: [main] DEBUG AbstractLdapPool.initialize(109) -  - beginning pool initialization

2015-06-30 09:48:10,083: [main] DEBUG AbstractLdapPool.initialize(117) -  - prune pool task scheduled

2015-06-30 09:48:10,084: [main] DEBUG AbstractLdapPool.initialize(125) -  - validate pool task scheduled

2015-06-30 09:48:10,084: [main] DEBUG AbstractLdapPool.initializePool(145) -  - checking ldap pool size >= 3

2015-06-30 09:48:10,106: [main] DEBUG AbstractLdapPool.initialize(131) -  - pool initialized to size 3

2015-06-30 09:48:10,174: [main] WARN  ApiConfig.printConfigOnce(227) -  - Grouper starting up: version: 2.1.5, build date: 2013/10/03 15:50:12, env: <no label configured>

grouper.properties read from: /etc/tomcat6/appconf/grouper.properties

Grouper current directory is: /usr/share/tomcat6

log4j.properties read from:   /etc/tomcat6/appconf/log4j.properties

Grouper is logging to file:   /usr/share/tomcat6/logs/grouper.log, at min level WARN for package: edu.internet2.middleware.grouper, based on log4j.properties

grouper.hibernate.properties: /etc/tomcat6/appconf/grouper.hibernate.properties

grouper.hibernate.properties: 

sources.xml read from:        /etc/tomcat6/appconf/sources.xml

sources.xml groupersource id: g:gsa

sources.xml groupersource id: grouperEntities

sources.xml ldap source id:   applications: ldap.properties

sources.xml ldap source id:   openconext-ldap: ldap.properties

Should I configure Grouper differently? sources.xml has a lot of different settings and I have been reluctant to make changes as I am not a grouper expert.

—
Reply to this email directly or view it on GitHub.