commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "bhupesh bansal (JIRA)" <j...@apache.org>
Subject [jira] Commented: (POOL-146) Thread deadlock issue in GenericKeyedObjectPool borrowObject()
Date Sun, 05 Jul 2009 21:15:14 GMT

    [ https://issues.apache.org/jira/browse/POOL-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727363#action_12727363
] 

bhupesh bansal commented on POOL-146:
-------------------------------------

Many Thanks Mark, 

Can you attach the patch to this bug ?? I would like to see the fix I spent considerable time
looking into the commons-pools code base and couldn't find the issue and yes global Latch
was not a solution I understood after looking into the code later. 

BTW have you looked into ArrayBlockingQueue from java 1.5.0 onwards in their concurrent package
?? I was thinking using that would clean up the code a lot ?

> Thread deadlock issue in GenericKeyedObjectPool borrowObject()
> --------------------------------------------------------------
>
>                 Key: POOL-146
>                 URL: https://issues.apache.org/jira/browse/POOL-146
>             Project: Commons Pool
>          Issue Type: Bug
>    Affects Versions: 1.5.1
>            Reporter: bhupesh bansal
>             Fix For: 1.5.2
>
>
> I am a new user of common-pools and I was having some weird behavior with GenericKeyedObjectPool
> GenericKeyedObjectPool: 1074:1077
>      public Object borrowObject(Object key) throws Exception {
>         long starttime = System.currentTimeMillis();
>         Latch latch = new Latch(key);     ---> This object is tried to be used for
managing pool size by calling wait()/notify() 
> My thinking is this should be a shared/global object and not created new for each call
?? 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message