Return-Path: X-Original-To: apmail-directory-dev-archive@www.apache.org Delivered-To: apmail-directory-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 77778108C9 for ; Wed, 31 Dec 2014 19:44:15 +0000 (UTC) Received: (qmail 43639 invoked by uid 500); 31 Dec 2014 19:44:16 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 43591 invoked by uid 500); 31 Dec 2014 19:44:16 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 43388 invoked by uid 99); 31 Dec 2014 19:44:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Dec 2014 19:44:13 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (athena.apache.org: local policy) Received: from [209.85.217.181] (HELO mail-lb0-f181.google.com) (209.85.217.181) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Dec 2014 19:44:06 +0000 Received: by mail-lb0-f181.google.com with SMTP id l4so13562172lbv.26 for ; Wed, 31 Dec 2014 11:41:06 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=45K5qeKGZXLMgdnqq5r37d1iyaYEwcnZRgcWkGLpDkY=; b=JzJH8GZyWXRCjrCDgK7/gcxHgTtxWyxf8CuKZ0Ul1lrExGrCh10SWLUKKdBbMR5o0o GN65XEQNTkjyehWyzEiGJOCUV9jhLHJUrXouzJZlOzam8RLTKOvaH/+wxmOpUXgpi8yR H6ij6zEavDR8MMyW3fYJySu1OY5SfiMgUVd3T6dIK076F+ejHnVzntZ/s93YG5i+M9bH zdUWYzJj5qMftLBRipcGOsT6IIC+WQ4YOOq0ycQJXyDYoY7WQ93hFRxGOReTrrFaYghd 3ywf8I+whNJAaMzzXNNuVGtI5Psr5sf49tmyx82zbTvNl5jl4Vq6EzkaT2CYX6etKMhS /rXQ== X-Gm-Message-State: ALoCoQl2j/Zcs0RUI2VH6bUCJorHU/p5jGJBM4W14JWpIW22ZoI+ewEeDwmhge8pc4LK1vO4TIAU MIME-Version: 1.0 X-Received: by 10.112.181.106 with SMTP id dv10mr63330783lbc.88.1420054866716; Wed, 31 Dec 2014 11:41:06 -0800 (PST) Received: by 10.25.167.132 with HTTP; Wed, 31 Dec 2014 11:41:06 -0800 (PST) X-Originating-IP: [108.28.237.28] In-Reply-To: References: <549E052A.1040602@gmail.com> <54A02A69.5060706@apache.org> Date: Wed, 31 Dec 2014 14:41:06 -0500 Message-ID: Subject: Re: Ldap pool issue... From: Lucas Theisen To: Apache Directory Developers List Content-Type: multipart/alternative; boundary=001a11c36d42e48815050b884993 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c36d42e48815050b884993 Content-Type: text/plain; charset=UTF-8 I just attempted to reproduce using: > I have done one more test : I'm now using only 2 threads, and set the maxIdle to 0. What happens is that after a few connections, only one thread is still accessing the server But the test completed successfully. I am running on windows with java 1.7.0_15... Is it supposed to succeed and i would only notice the log messages you mentioned? Or should i expect it to fail when it encounters one of those fail messages in the log? What is your log config to see those messages? Also, I was thinking about improving the performance of the ValidatingPoolableLdapConnectionFactory by maintaining an indicator as to whether a bind was called while the connection was checked out and only rebinding on return if it was. This could be a counter that gets incremented with each bind that the pool could check on return or even just a boolean that gets set to true when bind is called an can be set to false when the pool rebinds to the configured user. This could be done directly in the existing connection implementation or I could write a decorator to add the additional field. What do you think? --001a11c36d42e48815050b884993 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I just attempted to reproduce using:

>= I have done one more test : I'm now using only 2 threads, and set the= =20 maxIdle to 0. What happens is that after a few connections, only one=20 thread is still accessing the server

But the test completed su= ccessfully.=C2=A0 I am running on windows with java 1.7.0_15...=C2=A0 Is it= supposed to succeed and i would only notice the log messages you mentioned= ?=C2=A0 Or should i expect it to fail when it encounters one of those fail = messages in the log?=C2=A0 What is your log config to see those messages?
Also, I was thinking about improving the performance of the Val= idatingPoolableLdapConnectionFactory by maintaining an indicator as to whet= her a bind was called while the connection was checked out and only rebindi= ng on return if it was.=C2=A0 This could be a counter that gets incremented= with each bind that the pool could check on return or even just a boolean = that gets set to true when bind is called an can be set to false when the p= ool rebinds to the configured user.=C2=A0 This could be done directly in th= e existing connection implementation or I could write a decorator to add th= e additional field.=C2=A0 What do you think?


--001a11c36d42e48815050b884993--