Hi Heikki, Am 12.04.2011 14:09, schrieb Heikki Vatiainen: > On 04/11/2011 12:26 PM, Karl Gaissmaier wrote: > >>>> this is strange as Radiator-4.x has explicit support for reconnecting >>>> to ldap servers after an idle timeout. >>> >>> Indeed. The function that has "ldap search for ..." error message does >>> LDAP reconnect as the first thing. Reconnect should notice the closed >>> connection and then connect again. >> >> but not with HoldSeverConnection, or? I don't see a reconnect, >> not under Trace 4 and even not on the wire with wireshark. > > With HoldServerConnection, yes. > > When HoldServerConnection is defined and there should be an active ldap > handle, the code checks if the socket is still ok or it the socket > indicates that there is something available. If this something is > LDAP_OPERATIONS_ERROR with "Unexpected EOF" then there should be a > reconnect.
really strange. I didn't see this. After the LDAP upgrade I'll come back to this problem and keep you informed. Best Regards Charly -- Karl Gaissmaier Kommunikations und Informationszentrum kiz der Universität Ulm Abteilung Infrastruktur SG Netzwerk und Telekommunikation 89069 Ulm Tel.: 49(0)731/50-22499 Fax : 49(0)731/50-1222499 _______________________________________________ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator