My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 1163: Configurable timeout for LDAP connections (from the SshCommandStart threads)
2 people starred this issue and may be notified of changes. Back to list
Status:  Released
Owner:  ----
Closed:  Nov 2012


Sign in to add a comment
 
Project Member Reported by ziv...@gmail.com, Oct 28, 2011
Affected Version:
2.1.*
2.2.*

What steps will reproduce the problem?
1. LDAP system very slow

2. fire as many SSH commands as the value of the sshd.commandStartThreads parameter is. All SshCommandStart threads are then blocked waiting on LDAP.
As there is no explicit timeout defined the SshCommandStart threads will
wait indefinitely. Check here for confirmation that the default is "no timeout":
http://download.oracle.com/javase/jndi/tutorial/ldap/connect/config.html

3. Processing of all follow up SSH commands will be blocked.

What is the expected output? What do you see instead?
The wait on LDAP should interrupt after some amount of time. The
SSH command should fail. The thread is released for processing a next
request.

Please provide any additional information below.
Example on how to setup the timeout:
http://download.oracle.com/javase/tutorial/jndi/newstuff/readtimeout.html

We should introduce a parameter in the ldap section to make the timeout
configurable. For example:
[ldap]
    timeoutSeconds = 10
Nov 16, 2012
Project Member #1 choro...@wikimedia.org
This was done some time ago: https://gerrit-review.googlesource.com/#/c/30360/
Status: Released
Sign in to add a comment

Powered by Google Project Hosting