156623 - Disable LDAP lookups for a time period after LDAP connection fails

Status: NEW

(MailNews Core :: LDAP Integration, defect)

Description

[Gary Coady]

Build ID: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1a+) Gecko/20020708

When trying to type an address in the compose window while the LDAP server is
down, mozilla stalls when trying to look up part of the address with the LDAP
server if there is a delay in typing part of the email address. Eventually this
times out and the UI becomes responsive again. However, the same freeze can
happen a number of times even during typing the same email address. Extremely
annoying when it happens (this morning :-)

Suggestion: Perhaps disallow new connections to the LDAP server if a connection
to it already failed, if focus has not yet been transferred to another part of
the UI?

Related bugs
bug 79509 (minused) - this is not needed if LDAP lookups are async.
bug 103426 - might affect suggestion made above if focus is changed by autocomplete.

Comment 1

[Srilatha Moturi]

over to dmose

Comment 2

[Dan Mosedale (:dmosedale, :dmose)]

Yeah, I agree... this is quite irritating.

Comment 3

[Samir Gehani]

Mail triage team: nsbeta1-

Comment 4

[Ken Johanson]

This bugs seems pretty old - is noone experiencing this anymore? I am, always
have, buts its finally getting to me. My symptom may be different though - When
I change focus from the address fields (even after a successful match/completion
from a local addr book entry), and then focus on the message body to start
typing, the focus eventually goes back (gets stolen) to the next-empty
addr-line, apparently after the LDAP coonection times-out. VERY annoying because
have to delete the text that I was trying to type into the body, from the
address line, then pick where I left off.

Perhaps when focus hits the subject, body, etc, could we disallow arrd taking it
back?

Comment 5

[Sean Aitken]

This is happening to me too.  I have added my work LDAP server to my directory
repository.  When it's online and I'm connected via. VPN, it works great!
However, when I'm not VPN'ed in or the server is down, I can't even compose a
single email because of the lookups being attempted.

This is a serious flaw because by having that LDAP server configured, I can't
even send an email in a reasonable time. It gets my vote.

Comment 6

[Dan Mosedale (:dmosedale, :dmose)]

Assigning bugs that I'm not actively working on back to nobody; use SearchForThis as a search term if you want to delete all related bugmail at once.

Comment 7

[石庭豐 (Seak, Teng-Fong)]

I agree too.

As a workaround: put TB in offline mode, or disable autocomplete to look into LDAP server.  But the later workaround takes quite long to do.  It would be nice if some shortcut keys are associated with one of them.

Comment 8

[石庭豐 (Seak, Teng-Fong)]

I've just upgraded TB to 3.1 (in windows and Linux) and found that autocomplete is no longer jammed the second time when TB is sure that LDAP can't be reached.

Maybe this bug can be marked as closed?

Comment 9

[石庭豐 (Seak, Teng-Fong)]

Oh, I might be saying too fast ...

LDAP search on autocomplete is always on for every compose window.  But on the other hand, if we want TB to explicitly stop searching LDAP, we must provide an _explicit_way_ to make it search again, or else TB won't get the latest contact info from LDAP server once the server is reachable again.

However, such explicit way doesn't exist yet.