You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/11/20 13:00:02 UTC
[jira] [Commented] (TINKERPOP-2409) js: DriverRemoteConnection
never times out if server uri not available.
[ https://issues.apache.org/jira/browse/TINKERPOP-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17236131#comment-17236131 ]
ASF GitHub Bot commented on TINKERPOP-2409:
-------------------------------------------
spmallette opened a new pull request #1364:
URL: https://github.com/apache/tinkerpop/pull/1364
https://issues.apache.org/jira/browse/TINKERPOP-2409
A replacement for #1362 that includes a test for the behavior we want to see.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
> js: DriverRemoteConnection never times out if server uri not available.
> -----------------------------------------------------------------------
>
> Key: TINKERPOP-2409
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2409
> Project: TinkerPop
> Issue Type: Bug
> Components: javascript
> Affects Versions: 3.4.8
> Reporter: Philip
> Priority: Major
>
> constructor...
> const authenticator = new PlainTextSaslAuthenticator(userName,dbData.password)
> this.dc = new DriverRemoteConnection(connectionStrArray.join(''), \{ authenticator })
> this.graph = new Graph()
>
> function code...
> const g = this.graph.traversal().withRemote(this.dc)
> let count = await g.V().count().next()
> console.log(count)
>
> This works great with a connection but with no connection it failed with a crash error in 3.3.8 - not ideal but was manageable as code is always run as a dynamic object per. In 3.4.8 when there is no connection it never resolves or times out so it just hangs.
> I haven't found a work around as yet
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)