[
https://issues.apache.org/jira/browse/POOL-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727109#action_12727109
]
bhupesh bansal commented on POOL-146:
-------------------------------------
Yes...
they share the same socket pool (GenericKeyedObjectPool) keyed on nodeId for
server A /B.
my understanding is threads blocked on Key A (slow server) should not cause
thread blocking for Key B ?? Is this assumption correct.
> 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.
