[
https://issues.apache.org/jira/browse/CONNECTORS-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13890645#comment-13890645
]
Karl Wright commented on CONNECTORS-878:
----------------------------------------
After some thought, I think the right way to tackle this problem is to keep a
running count of the number of active pools referencing a connection bin.
Then, the limit allowed for each pool is the maximum connections divided by the
number of active pools, rounded down.
A reasonable way to keep track of this information seems to me to be keeping
track in ConnectionBin of when a pool counter transitions from zero to 1, or
visa versa. Whenever this happens, the number of active pools should be
incremented or decremented, respectively. I'll give this a try and see if
seems to work as expected.
> Throttled connection pooling is currently disabled; we should address the
> issues and turn it back on
> ----------------------------------------------------------------------------------------------------
>
> Key: CONNECTORS-878
> URL: https://issues.apache.org/jira/browse/CONNECTORS-878
> Project: ManifoldCF
> Issue Type: Bug
> Components: Framework core
> Affects Versions: ManifoldCF 1.6
> Reporter: Karl Wright
> Assignee: Karl Wright
> Fix For: ManifoldCF 1.6
>
>
> r1564151 committed a hack designed to unblock release 1.5. See
> CONNECTORS-872 for a description as to why the hack was necessary. We need
> to find a better way.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
