[jira] [Commented] (TINKERPOP-2488) Using ws:// when Neptune requires wss:// doesn't throw exception

["Stephen Mallette (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TINKERPOP-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17296338#comment-17296338 ] 

Stephen Mallette commented on TINKERPOP-2488:
---------------------------------------------

Wondering if this is fixed in 3.4.9. I added some tests in this vein:

https://github.com/apache/tinkerpop/commit/7bfe54a64d456141ce805f68fbc9d3e17c8f818d

and they passed locally, but there were problems prior to this version where some network problems wouldn't surface as errors and appear to just do nothing. I wonder if that's the problem here. Given that I have some working tests around this now, I'm going to assume that things are working properly now with the latest version. If not, please feel free to reopen.

> Using ws:// when Neptune requires wss:// doesn't throw exception
> ----------------------------------------------------------------
>
>                 Key: TINKERPOP-2488
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2488
>             Project: TinkerPop
>          Issue Type: Bug
>          Components: javascript
>    Affects Versions: 3.4.8
>            Reporter: Mark Richman
>            Priority: Minor
>
> When using the JavaScript driver, attempting to connect to Neptune via {{ws://}} when Neptune requires {{wss://}} does not throw an exception. The process simply exits silently.
> {code:java}
> #!/usr/bin/env node
> import pkg from 'gremlin';
> const { structure, process, driver } = pkg;
> const Graph = structure.Graph;
> const __ = process.statics;
> const { t, order, cardinality, column, scope, pop, operator, P, traversal } = process;
> const hostname = 'neptunecluster.cluster-xxxxxxxxx.us-east-1.neptune.amazonaws.com'
> const port = 8182
> const wspath = `ws://${hostname}:${port}/gremlin`; // doesn't throw exception if wss:// is required
> const DriverRemoteConnection = driver.DriverRemoteConnection;
> const connection = new DriverRemoteConnection(wspath, {});
> const g = traversal().withRemote(connection);
> const result = await g.V().hasLabel("person").toList()
> console.log(result)
> {code}
>  
>  Note: using Node.js as a shell script like this requires {{"type": "module"}} in {{package.json}}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)