[ 
https://issues.apache.org/jira/browse/TINKERPOP3-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stephen mallette closed TINKERPOP3-877.
---------------------------------------
    Resolution: Fixed

Ok this should be resolved. Seems like it was hanging when the websocket 
handshake couldn't be made due to the invalid SSL setting on the driver side.  
Working better now - at least we get a {{TimeoutException}} now:

{code}
gremlin> cluster = org.apache.tinkerpop.gremlin.driver.Cluster.build().create()
==>localhost/127.0.0.1:8182
gremlin> client = cluster.connect()
==>org.apache.tinkerpop.gremlin.driver.Client$ClusteredClient@1a1ed4e5
gremlin> client.init()
WARN  org.apache.tinkerpop.gremlin.driver.Client  - Could not initialize 
connection pool for Host{address=localhost/127.0.0.1:8182, 
hostUri=ws://localhost:8182/gremlin} - will try later
==>org.apache.tinkerpop.gremlin.driver.Client$ClusteredClient@1a1ed4e5
gremlin> client.submit("1+1").all().get()
java.lang.RuntimeException: java.util.concurrent.TimeoutException: Timed out 
waiting for an available host.
Display stack trace? [yN] y
{code}

> Driver hangs if SSL enabled on server but not on client
> -------------------------------------------------------
>
>                 Key: TINKERPOP3-877
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-877
>             Project: TinkerPop 3
>          Issue Type: Bug
>          Components: driver
>    Affects Versions: 3.0.1-incubating
>            Reporter: stephen mallette
>            Assignee: stephen mallette
>            Priority: Minor
>             Fix For: 3.0.2-incubating
>
>
> Start Gremlin Server with SSL turned on, then try to connect with:
> {code}
> cluster = org.apache.tinkerpop.gremlin.driver.Cluster.build().create()
> client = cluster.connect()
> client.init()
> {code}
> The {{init()}} (or {{submit()}} for that matter) just hangs - would be nice 
> to get a "You'd best enable SSL, fool!"  kind of message .  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to