Question

How can we manually configure--at the code level--the LdapContrib plugin to never build its own cache?

Our LdapContrib installation continues to build its cache, daily (the default), despite our setting of '0' for Maximum Cache Age (in the configuration panel). We have to wait 25 minutes each morning, after initial attempt to access the TWiki, for the plugin to pull over 100K users from the LDAP.

We have a cron job that builds this cache during off-hours, which is what we would want it to do; it runs fine. So all we want now is to completely disable the plugin from running its own cache.

This wasn't an issue when we were using TWiki v4.1.2.

Any help would be greatly appreciated.

Environment

-- ShivaGoudarzi - 08 Feb 2008

Answer

If you answer a question - or have a question you asked answered by someone - please remember to edit the page and set the status to answered. The status is in a drop-down list below the edit box.

Looking into it.

100k, is this the size of the cache.db file? 100k net data is not much. There's no reason that downloading this amount of data should take 25 minutes. My test engine generates an LDAP cache of 2.8M containing roughly 10.000 keys within 16 seconds (both, TWiki and LDAP on the same machine, legacy hardware).

-- MichaelDaum - 14 Feb 2008

I can confirm this bug. Filed as Bugs:Item5365, also reported at SetMaxCacheAgeToInfinite. Will be fixed in next release.

-- MichaelDaum - 14 Feb 2008

Fixed in latest release 2.99.4

-- MichaelDaum - 14 Feb 2008

Thank you; we have installed the release, and will test and report results.

FYI- About 100K question: We have over 100K records/users to pull from OID, which creates delay in cache refresh.

-- ShivaGoudarzi - 15 Feb 2008

Okay, that's 10x more records than my regular testset has got. Should be about 3 minutes to download them, roughly.

-- MichaelDaum - 18 Feb 2008

Patch seems to work; thanks!

-- ShivaGoudarzi - 19 Feb 2008

We installed the patch, yet after a few days, the cache started building itself again! We still have the Max Cache Age at 0.

-- ShivaGoudarzi - 20 Feb 2008