Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4FDC4EFCA for ; Wed, 20 Feb 2013 14:15:13 +0000 (UTC) Received: (qmail 3540 invoked by uid 500); 20 Feb 2013 14:15:10 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 3338 invoked by uid 500); 20 Feb 2013 14:15:09 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 3314 invoked by uid 99); 20 Feb 2013 14:15:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Feb 2013 14:15:08 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of cedric.couralet@gmail.com designates 209.85.217.171 as permitted sender) Received: from [209.85.217.171] (HELO mail-lb0-f171.google.com) (209.85.217.171) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Feb 2013 14:15:03 +0000 Received: by mail-lb0-f171.google.com with SMTP id gg13so6052647lbb.30 for ; Wed, 20 Feb 2013 06:14:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:content-transfer-encoding; bh=P+m63URiKHFQrvZTdSle5Qn5zhifhls1XCNse0vNgD4=; b=xihX77vUZrz240cswVLhqP8yD59xGSGZYNpPMZUlt6TH70Taxyof00mXJgnuJJAbBp M8cwmBfzd0vT/JAX67dk2K5Oq4sS8EAtkaN/anRrEoJIPus1au/0CQ46brNbEWgF034K P0e1L4EvfM4xRWuDjZpOp0JzWJUBTRFo+sT67EjrrUeu7PFqw+qTlPtQzvWjfj80MecP Ye4cZ/y+gNa/wPADPJChYB+DuSk7YtENk6dd0JHfDgkypMgtQTUBZb59xnUr0Espu1dN XcwJKS/tUG1sT9AyQi5nnh5yMDS/Qc3eViDtvVSWbGU7Yi6xxHXB2EqqSBz/a7EZOnut 8bcw== MIME-Version: 1.0 X-Received: by 10.152.144.202 with SMTP id so10mr18091254lab.9.1361369682108; Wed, 20 Feb 2013 06:14:42 -0800 (PST) Received: by 10.112.3.38 with HTTP; Wed, 20 Feb 2013 06:14:41 -0800 (PST) In-Reply-To: References: Date: Wed, 20 Feb 2013 15:14:41 +0100 Message-ID: Subject: Re: Question regarding JNDIRealm - tomcat 6.0.35 From: =?ISO-8859-1?Q?C=E9dric_Couralet?= To: Tomcat Users List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org 2013/2/20 Tanmoy Chatterjee : > Thanks C=E9dric, I will try this and let you know. > Once Ldap closes the connection from it's end, tomcat indeed keeps on try= ing and finally establishes a new connection....but the time spent in retr= ying is too high (more than 4-5 minutes) and in that time...user cannot log= in....the login page just sort of hangs in the browser. > I'd say this is more a problem with openldap. Do you know why tomcat hangs to recreate the connection when openldap closes it? Do you have anything in openldap configuration which could explain this. We are at the moment migrating our old ldap server to openldap and this could be a real issue for us. Just a note, from what I see, Tomcat does not keep on trying. A first attempt is made on the context then if an exception is thrown, it is caught and tomcat call the open method again (wich tries first the connectionURL and then the alternateUrl if problem). So only two attempts if I'm not wrong. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org