[
https://issues.apache.org/jira/browse/TINKERPOP-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette closed TINKERPOP-1191.
---------------------------------------
Resolution: Won't Fix
Fix Version/s: (was: 3.1.2-incubating)
(was: 3.2.0-incubating)
Going to re-write this a different way - not sure that there's a concrete way
to say that reconnect isn't possible given the retry nature of the reconnect
process. Doesn't really make sense as written.
> Better identify when reconnect isn't possible
> ---------------------------------------------
>
> Key: TINKERPOP-1191
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1191
> Project: TinkerPop
> Issue Type: Improvement
> Components: driver
> Affects Versions: 3.1.1-incubating
> Reporter: stephen mallette
> Assignee: stephen mallette
>
> There are times when a connection to the server can recover and there are
> times when it can't ever - like when you try to connect to an ssl-enabled
> server with a client not configured for ssl. In those latter cases, the user
> should get a better error explaining things. Right now, in the case of the
> SSL example, they get a {{TimeoutException}} because the host gets marked as
> dead when the driver can't connect and the pool is thus ignored.
> As a side of working on this, the message for trying to get a connection from
> a pool with no hosts should be improved. That's pretty easy to detect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
