Skip to Content.
Sympa Menu

grouper-users - [grouper-users] AD/LDAP timeout sources.xml

Subject: Grouper Users - Open Discussion List

List archive

[grouper-users] AD/LDAP timeout sources.xml


Chronological Thread 
  • From: Jared Hoffman <>
  • To: Gouper Users <>
  • Subject: [grouper-users] AD/LDAP timeout sources.xml
  • Date: Wed, 13 Sep 2017 10:37:45 -0400
  • Ironport-phdr: 9a23:/VKiHhaHw61/Z3jQCSdTBG7/LSx+4OfEezUN459isYplN5qZr8S9bnLW6fgltlLVR4KTs6sC0LuG9fi4EUU7or+5+EgYd5JNUxJXwe43pCcHRPC/NEvgMfTxZDY7FskRHHVs/nW8LFQHUJ2mPw6arXK99yMdFQviPgRpOOv1BpTSj8Oq3Oyu5pHfeQtFiT6+bL9oMBm6sRjau9ULj4dlNqs/0AbCrGFSe+RRy2NoJFaTkAj568yt4pNt8Dletuw4+cJYXqr0Y6o3TbpDDDQ7KG81/9HktQPCTQSU+HQRVHgdnwdSDAjE6BH6WYrxsjf/u+Fg1iSWIdH6QLYpUjm58axlVAHnhzsGNz4h8WHYlMpwjL5AoBm8oxBz2pPYbJ2JOPZ7eK7WYNEUSndbXstJVyJPDICyYZYRAeUdJutXtZXxqkEUoBeiGQWhBuXiwSJIiH/s2q061vwsHwXc0ww6Ad0BrWnfotfyNKccX+C1ybPHzTPeZP5R2Tf974bIch4kof6WW7Jwc9HcyUoxGAPDjlSQrorlMymL2esQrmiW9uxtXv+hhW4grgF+uDmvxsE0h4nGnIIVzU3E9T1nz4YvP9G3UlZ7Yca8HJtRsSGaK5V5QtkkQ252pCY21KcKtoCmcygX0JgnxRnfZOedc4iV5BLjT+aRLil8hHJhYr6/nQuy8U6mx+bhVce0yE5HojdLn9TPrHwByR/e5tKaRvdn8Eqs3S6D2x7P5uxAO0w5lqrWJ4Q/zrItlpcfq0XOEyvwlU7rlqGZbF8k9fKt6+n/YrXpuJucN4hshwH7KKsum8i/AesiPQgSQWeW+f6w1L798k3/QLRKifs2nrPHv5/HOMQXvq+5AwlL3YY/8xuzEjmr3dcCkXUZL19JYg+Lg5LnNlzKOPz4CO2wg1WokDdl3fDGObjhD43NLnjEnrfhc7N95FRayAox1t1f5IxbCrcBIfL0XE/9rsLXAQIkMwCs2eboFM191p8CWWKIGqKZP7nSsViV5uI3PeaMfpYZuCvmK/c7/f7ulmQ0mVscfamywZsXc260Eu5nI0WffXrjnM0BEWEUsQoiUuDmkkONXiNOZyX6Y6VpyTYmEI+8RbrYS5q2yOiOxiCmBpBMI31dB0qXOXbua4ieXfoQMmSfLtI3wRIeUr30aYY72B3mlAj0xb9uKKKA+ioWu5fq0tpd5ODVhBY0szF4EpLOgCm2U2hokzZQFHcN16dlrBk4kw/b3A==

When we have several grouper loader jobs running we occasionally get timed out errors for some loader jobs. We still use the sources.xml config (plan on patching to current in October break maintenance window). 

The "timeout used" in the error is -1, so I'm wondering if that is an unlimited timeout. Or if there is a timeout setting we haven't found. We tried adding "ldap.personLdap.timeout = 5000" to grouper-loader.properties, but I think that needs to be closer to the sources.xml AD/LDAP config.  

I read through this thread from the list but we don't have an ldap.properties config. We are using the sources.xml config. Do we need to get all the current patches to be able to set the timeout properly? I could schedule a special maintenance to patch if it would be easier to manage.
https://lists.internet2.edu/sympa/arc/grouper-users/2016-12/msg00058.html





edu.internet2.middleware.subject.SourceUnavailableException: Ldap NamingException: LDAP response read timed out, timeout used:-1ms.
at edu.internet2.middleware.subject.provider.LdapSourceAdapter.getLdapResultsHelper(LdapSourceAdapter.java:775)
at edu.internet2.middleware.subject.provider.LdapSourceAdapter.getLdapResults(LdapSourceAdapter.java:662)
at edu.internet2.middleware.subject.provider.LdapSourceAdapter.getLdapUnique(LdapSourceAdapter.java:807)
at edu.internet2.middleware.subject.provider.LdapSourceAdapter.getSubjectByIdentifier(LdapSourceAdapter.java:437)
at edu.internet2.middleware.subject.provider.BaseSourceAdapter.getSubjectsByIdentifiers(BaseSourceAdapter.java:197)
at edu.internet2.middleware.grouper.subj.SourcesXmlResolver$7.callLogic(SourcesXmlResolver.java:1009)
at edu.internet2.middleware.grouper.subj.SourcesXmlResolver$7.callLogic(SourcesXmlResolver.java:1006)
at edu.internet2.middleware.grouper.subj.SourcesXmlResolver$LogLabelCallable.call(SourcesXmlResolver.java:169)
at edu.internet2.middleware.grouper.subj.SourcesXmlResolver.executeCallables(SourcesXmlResolver.java:230)
at edu.internet2.middleware.grouper.subj.SourcesXmlResolver.findByIdentifiers(SourcesXmlResolver.java:1015)
at edu.internet2.middleware.grouper.subj.CachingResolver.findByIdentifiers(CachingResolver.java:811)
at edu.internet2.middleware.grouper.subj.ValidatingResolver.findByIdentifiers(ValidatingResolver.java:282)
at edu.internet2.middleware.grouper.SubjectFinder.findByIdentifiers(SubjectFinder.java:604)
at edu.internet2.middleware.grouper.app.loader.db.GrouperLoaderResultset.bulkLookupSubjects(GrouperLoaderResultset.java:201)
at edu.internet2.middleware.grouper.app.loader.GrouperLoaderType$3.runJob(GrouperLoaderType.java:458)
at edu.internet2.middleware.grouper.app.loader.GrouperLoaderJob.runJob(GrouperLoaderJob.java:423)
at edu.internet2.middleware.grouper.app.loader.GrouperLoaderJob.execute(GrouperLoaderJob.java:323)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573)
Caused by: javax.naming.NamingException: LDAP response read timed out, timeout used:-1ms.; remaining name 'CN=Users,DC=kenyon,DC=edu'
at com.sun.jndi.ldap.Connection.readReply(Connection.java:483)
at com.sun.jndi.ldap.LdapClient.getSearchReply(LdapClient.java:639)
at com.sun.jndi.ldap.LdapClient.search(LdapClient.java:562)
at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:1985)
at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1847)
at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1772)
at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1789)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:412)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:394)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:376)
at edu.vt.middleware.ldap.AbstractLdap.search(AbstractLdap.java:215)
at edu.vt.middleware.ldap.Ldap.search(Ldap.java:431)
at edu.vt.middleware.ldap.Ldap.search(Ldap.java:347)
at edu.internet2.middleware.subject.provider.LdapSourceAdapter.getLdapResultsHelper(LdapSourceAdapter.java:772)
... 18 more


--
Jared Hoffman • Associate Director for Enterprise Infrastructure
Information Technology Services • Kenyon College
740.427.5948






Archive powered by MHonArc 2.6.19.

Top of Page