[
https://issues.apache.org/jira/browse/TINKERPOP-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florian Hockmann closed TINKERPOP-2215.
---------------------------------------
Fix Version/s: 3.4.7
3.5.0
Resolution: Fixed
This was actually fixed by [~dzmitry.lahoda] in this PR:
[https://github.com/apache/tinkerpop/pull/1254]
I completely forgot about this ticket when I reviewed and merged that PR.
> Better exception message for connection problems
> ------------------------------------------------
>
> Key: TINKERPOP-2215
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2215
> Project: TinkerPop
> Issue Type: Improvement
> Components: dotnet
> Affects Versions: 3.4.1
> Reporter: Florian Hockmann
> Priority: Minor
> Fix For: 3.5.0, 3.4.7
>
>
> The {{ConnectionPool}} currently checks whether the pool is empty and then
> tries to retrieve an available connection if it is not empty. If this fails,
> then a {{ConnectionPoolBusyException}} is thrown with this text:
> {quote}All 4 connections have reached their MaxInProcessPerConnection limit
> of 32. Consider increasing either the PoolSize or the
> MaxInProcessPerConnection limit.
> {quote}
> However, this exception can also be thrown if all connections in the pool
> were already closed and were therefore removed from the pool. The exception
> message doesn't make sense in this case.
> A different exception should be thrown if the pool only contained already
> closed connections as it's important for users to know whether they actually
> executed too many requests in parallel or whether there is a connection
> problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
