Bug #71686 | Web interface dies on failed LDAP login | ||
---|---|---|---|
Submitted: | 12 Feb 2014 19:58 | Modified: | 14 Apr 2014 12:10 |
Reporter: | Daniël van Eeden (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Enterprise Monitor: Web | Severity: | S2 (Serious) |
Version: | 3.0.5, 3.0.6 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | LDAP |
[12 Feb 2014 19:58]
Daniël van Eeden
[13 Feb 2014 6:43]
Daniël van Eeden
Set to S2 (Serious).
[16 Feb 2014 17:21]
Daniël van Eeden
In the service manager graph "HTTP Server Service Times" there are spikes of 15 minutes and 30 seconds when this happens.
[16 Feb 2014 17:22]
Daniël van Eeden
HTTP Server Service Times graph
Attachment: srvman_ldap_issue.png (image/png, text), 53.89 KiB.
[21 Feb 2014 10:25]
Mark Leith
Verifying as described via some code inspection. Additional info on the actual exception being raised: javax.naming.ServiceUnavailableException: <ldap_server>:636; socket closed; remaining name 'cn=<user>,ou=Users,o=<company>' at com.sun.jndi.ldap.Connection.readReply(Unknown Source)
[27 Feb 2014 9:56]
Daniël van Eeden
add LDAP tag
[14 Apr 2014 12:10]
Daniël van Eeden
From the 3.0.8 release notes: ---------------------------------------------- It is now possible to configure the LDAP connection timeout values. The following were added to the LDAP Authentication frame of the Global Settings page: Connect timeout: time elapsed without establishing a connection to the LDAP server. If a connection is not established within the defined number of seconds, an error is returned. Read timeout: time elapsed without a response to a request for data from the LDAP server. If no response is received within the defined number of seconds, an error is returned. Note If the value is set to 0, the timeout value defaults to the operating system's default value. (Bug #18287809) ---------------------------------------------- This indeed improves the handling of read timeouts a lot :)