Return-Path: Delivered-To: apmail-jakarta-commons-user-archive@www.apache.org Received: (qmail 78453 invoked from network); 9 Jan 2007 06:58:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Jan 2007 06:58:22 -0000 Received: (qmail 30064 invoked by uid 500); 9 Jan 2007 06:58:25 -0000 Delivered-To: apmail-jakarta-commons-user-archive@jakarta.apache.org Received: (qmail 30001 invoked by uid 500); 9 Jan 2007 06:58:25 -0000 Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Users List" Reply-To: "Jakarta Commons Users List" Delivered-To: mailing list commons-user@jakarta.apache.org Received: (qmail 29987 invoked by uid 99); 9 Jan 2007 06:58:24 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Jan 2007 22:58:24 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [216.222.200.2] (HELO buzz.frogspace.net) (216.222.200.2) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Jan 2007 22:58:14 -0800 Received: from tbee.dyndns.org ([82.92.119.213] helo=[10.0.0.100]) by buzz.frogspace.net with esmtp (Exim 4.44) id 1H4Avi-0002K3-08 for commons-user@jakarta.apache.org; Mon, 08 Jan 2007 22:57:54 -0800 Message-ID: <45A33CF5.5050206@tbee.org> Date: Tue, 09 Jan 2007 07:57:57 +0100 From: Tom User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Jakarta Commons Users List Subject: Re: Commons Pool.. anyone using? References: <20070109014344.1035895146@mail.digipixart.com> In-Reply-To: <20070109014344.1035895146@mail.digipixart.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 82.92.119.213 X-SA-Exim-Mail-From: tbee@tbee.org X-Virus-Checked: Checked by ClamAV on apache.org I've been using commons pool a lot for the last years and found that with "infinite" objects it works perfectly (so a pool factory that keeps generating new objects, the effective maximum is managed by the pool). However with a limited pool it does not work (for example 3 named services, which might be the case when using SOAP): I've posted examples here that show that the current implementation goes into an infinite loop, but I don't know if that was fixed by now. This however forced me to write an alternative implementation based on the same interfaces. Tom Barrie Selack wrote: > I was looking at Commons Pool for some SOAP/HTTP connection objects. Is > anyone using Pool/ Any hint/tips/warnings etc? > > Regards, > barrie > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org > For additional commands, e-mail: commons-user-help@jakarta.apache.org > > > --------------------------------------------------------------------- To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-user-help@jakarta.apache.org