You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Mark Thomas (JIRA)" <ji...@apache.org> on 2009/07/02 14:53:47 UTC
[jira] Commented: (POOL-146) Thread deadlock issue in
GenericKeyedObjectPool borrowObject()
[ https://issues.apache.org/jira/browse/POOL-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12726465#action_12726465 ]
Mark Thomas commented on POOL-146:
----------------------------------
Am I correct in thinking that your have a single pool of sockets that clients use to connect to either Server A or Server B?
> 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
>
> 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.