Mailing-List: contact user-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Users List" <user@commons.apache.org>
Received-SPF: pass (nike.apache.org: domain of phil.steitz@gmail.com
 designates 209.85.220.54 as permitted sender)
Message-ID: <5228E037.4020709@gmail.com>
Date: Thu, 05 Sep 2013 12:49:11 -0700
From: Phil Steitz <phil.steitz@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Commons Users List <user@commons.apache.org>
Subject: Re: Apache Commons Pool performance issue
References: <1378397337847-4653614.post@n4.nabble.com>
 <5228AE37.1030905@gmail.com> <5228B00A.3030502@apache.org>
 <1378400315924-4653619.post@n4.nabble.com>
In-Reply-To: <1378400315924-4653619.post@n4.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 9/5/13 9:58 AM, Programmer wrote:
> Thanks for the reply guys.
>
> I use 1.6 JAR in my classpath. Is there anyway I can verify the 'when
> exhausted action' at run time?

As Mark said, based on the line numbers in the stack trace, it is
pretty certain that you are in fact running 1.3.  Moreover, the
exhausted action *must* be block to get to the line where the thread
in the trace is waiting.

Phil
>
>
>
> --
> View this message in context: http://apache-commons.680414.n4.nabble.com/Apache-Commons-Pool-performance-issue-tp4653614p4653619.html
> Sent from the Commons - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
> For additional commands, e-mail: user-help@commons.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org