[Building Sakai] LDAP caching

[Kusnetz, Jeremy]

Thanks Sam.

I'm probably missing something here, but can I override the default of 5 minutes?

Shouldn't memory.edu.amc.sakai.user.JLDAPDirectoryProvider.userCache=timeToLiveSeconds=14400,timeToIdleSeconds=3600,maxElementsInMemory=20000
Have set it to 14400 seconds?  If so, it's not acting that way.

I do see in JLDAPDirectoryProvider.java public static final long DEFAULT_CACHE_TTL = 5 * 60 * 1000;
But I also see that there is a setCacheTTL which should be able to override it.


From: Sam Ottenhoff [mailto:ottenhoff at longsight.com]
Sent: Friday, December 20, 2013 11:24 AM
To: Kusnetz, Jeremy
Cc: sakai-dev Developers
Subject: Re: [Building Sakai] LDAP caching



Looking at the LDAP debug logs we see that the entry is found in the cache but it's expired?  This is only after a few minutes after doing the initial lookup from the LDAP server.


Yes, the default is an incredibly low 5 minutes.  If others support increasing this cache default time, let's file a JIRA and raise the default.

We added to sakai.properties:
memory.edu.amc.sakai.user.JLDAPDirectoryProvider.userCache=timeToLiveSeconds=14400,timeToIdleSeconds=3600,maxElementsInMemory=20000


I believe we should just remove this JLDAP cache in favor of caching in the central UserDirectoryService.  So I would just zero out this JLDAP cache and then increase the central cache like this:

memory.org.sakaiproject.user.api.UserDirectoryService.callCache=timeToLiveSeconds=43200,timeToIdleSeconds=0,maxElementsInMemory=50000

This message is private and confidential. If you have received it in error, please notify the sender and remove it from your system.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20131220/424fd3b6/attachment.html