https://issues.apache.org/bugzilla/show_bug.cgi?id=54587

--- Comment #16 from Christian Knierim <[email protected]> ---
The bug still might cause some errors. The occurrence is more seldom.

Let me explain with an example from one of our tests yesterday:

Connection to LDAP is established
[Mon Mar 04 14:46:33.147055 2013] [authnz_ldap:debug] [pid 10701]
mod_authnz_ldap.c(593): [client 10.54.1.199:59811] AH01697: auth_ldap
authenticate: accepting m051021

Client-Connect uses LDAP-authenticate, but this time user (m052246) is already
in cache
[Mon Mar 04 15:06:17.950988 2013] [authnz_ldap:debug] [pid 10701]
mod_authnz_ldap.c(593): [client 10.54.1.199:59884] AH01697: auth_ldap
authenticate: accepting m052246

Now the new patch “reuse.diff” will take place, with “Removing connection”.
Please note that the “2000 seconds ago” is calculated from 15:06 to 15:39.
But at 15:06, the LDAP server was not really asked. So the connection was in
fact idle from 14:46 to 15:39. The server will close after one hour. Good luck
this time.
[Mon Mar 04 15:39:38.356157 2013] [ldap:trace1] [pid 10701] util_ldap.c(732):
[client 10.58.230.5:45009] Removing LDAP connection last used 2000 seconds ago
[Mon Mar 04 15:39:38.356591 2013] [authnz_ldap:debug] [pid 10701]
mod_authnz_ldap.c(501): [client 10.58.230.5:45009] AH01691: auth_ldap
authenticate: using URL
ldaps://ldapqsu.xxx.xxx.de:636/ou=people,dc=hvb,dc=de?uid?one?(objectclass=hvb-userextension)
[Mon Mar 04 15:39:38.356637 2013] [authnz_ldap:trace1] [pid 10701]
mod_authnz_ldap.c(522): [client 10.58.230.5:45009] auth_ldap authenticate:
final authn filter is (&(objectclass=hvb-userextension)(uid=m052237))
[Mon Mar 04 15:39:38.356659 2013] [authnz_ldap:debug] [pid 10701]
mod_authnz_ldap.c(593): [client 10.58.230.5:45009] AH01697: auth_ldap
authenticate: accepting m052237

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to