[
https://issues.apache.org/jira/browse/TINKERPOP-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette updated TINKERPOP-1999:
----------------------------------------
Fix Version/s: (was: 3.3.3)
(was: 3.3.2)
> [Java][gremlin-driver] Query to a remote server via the websocket client
> hangs indefinitely if the server becomes unavailable
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: TINKERPOP-1999
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1999
> Project: TinkerPop
> Issue Type: Bug
> Components: driver
> Affects Versions: 3.3.2, 3.3.3
> Reporter: Ankesh Khandelwal
> Priority: Minor
>
> Query to a remote server via the websocket client hangs indefinitely if the
> server becomes unavailable.
>
> Consider the code snippet below.
>
>
> {code:java}
> // Create a websocket client
> final Client client =
> Cluster.build().addContactPoint(<endpoint>).create().connect();
> // submit a query
> ResultSet resultSet = client.submit("g.V().id()");
> // wait for all the results
> resultSet.all().join();
>
> {code}
>
> If the
> {code:java}
> client.submit(...){code}
> call succeeds (that is the server is available/reachable) but before getting
> the results from the server, the server becomes unavailable/unreachable, then
> the client code hangs indefinitely at
> {code:java}
> resultSet.all().join(){code}
> .
> The right behavior would be to throw an exception indicating the server is
> not available anymore. The hanging behavior suggests that the
> *channelInactive* call from websocket connection may not be getting
> propagated properly (perhaps getting swallowed somewhere).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
