https://issues.apache.org/bugzilla/show_bug.cgi?id=47841
Edward <edward.qu...@igindex.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |
--- Comment #2 from Edward <edward.qu...@igindex.co.uk> 2009-11-23 01:53:21 UTC
---
(In reply to comment #1)
> In the scenario you describe, with the configuration provided, Tomcat will try
> the UserdatabaseRealm first and then the JNDIRealm.
>
> If the LDAP server isn't available, then Tomcat will wait for the connection
> to
> time out.
>
> The timeout is not currently configurable. It is debatable how useful that
> would be since if the LDAP server was down, you system is likely to have real
> issues.
>
> If you have a use case where configuring the timeout would be useful, please
> create an enhancement request. Enhancement requests with patches and a good
> justification usually get looked at faster.
Mark,
Thanks for your reply.
I tested this again, and what surprises me is that if LDAP were down (I
simulated this by changing the ldap port number in jndi.connectionURL), then
Tomcat won't serve anything. Surely non-protected content should be served
regardless of what is going on with LDAP, but I can't even get to the tomcat
home page.
I can think of 2 reasons to add a configurable timeout for LDAP:
1. To stop tcp requests stacking up on the server.
2. To aid the user trying to log in, at least realise there's a problem on the
server side (and not the client).
Regards,
Edward.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
