Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Wed, 21 Dec 2011 17:45:32 +0000 (UTC)
From: "Phil Steitz (Closed) (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: 
 <536360562.36174.1324489532171.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1558914559.14568.1314298109503.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Closed] (POOL-189) close() does not release threads blocked
 on borrowObject()
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/POOL-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Phil Steitz closed POOL-189.
----------------------------

    
> close() does not release threads blocked on borrowObject()
> ----------------------------------------------------------
>
>                 Key: POOL-189
>                 URL: https://issues.apache.org/jira/browse/POOL-189
>             Project: Commons Pool
>          Issue Type: Bug
>    Affects Versions: 1.5.6
>         Environment: java 1.6.0_24
>            Reporter: Adrian Nistor
>             Fix For: 1.5.7
>
>         Attachments: BUG-189v1.diff, BUG-189v2.diff, Test.java
>
>
> Hi,
> When I call close() and borrowObject() concurrently with no objects in
> the pool, close() will finish but borrowObject() is blocked forever.
> The documentation of close() mentions that borrowObject() should fail 
> with IllegalStateException, so I would expect the waiting threads to 
> throw IllegalStateException.
> I will attach a test that exposes this problem. For this test, the 
> expected output is:
> 0
> 1
> 2
> ...
> 4999
> DONE
> But when the bug manifests (almost always for this test), the output 
> is:
> 0
> 1
> 2
> The test does not finish, it just gets stuck after printing several 
> values.
> Is this a bug or am I reading the documentation wrongly? Is there 
> a patch for this?
> Thanks!
> Adrian

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira