Handling "connection error" about simpleddp HOT 6 CLOSED

Try to use try {await server.connect()} catch(error) {/*error logic here*/}

from simpleddp.

Still hangs forever on node.js 12.

It never throws.. You can reproduce this way:

import ws from 'isomorphic-ws'
import simpleDDP from 'simpleddp'

const opts = {
  endpoint: 'wss://google.com',
  SocketConstructor: ws,
  reconnectInterval: 500,
};

DDP = new simpleDDP(opts, [simpleDDPLogin]);

;(async () =>{
  try {
    console.log("will hang")
    await DDP.connect()
    console.log("this never gets logged!")
  } catch(error) {
    console.log("this never happens too", error)
  }

  console.log("executed 2")
})()

On the Chrome browser, I get a console.error that comes from socket.js to the console but it doesn't throw / get caught as well:

Does it catch for you?

from simpleddp.

If i set a "maxTimeout" then i get a Error as you can see on the [your source code here](maxTimeout: 1000) but that error has no message, but i can see the socket.js stays retrying anyway, maybe "socket.close" should also be called when the max timeout is reached?

Does the same happen to you?

from simpleddp.

The error happens earlier because by default simpleDDP will try to connect to the endpoint and you are not putting new simpleDDP(opts, [simpleDDPLogin]) in a try block, but you can prevent the default with autoConnect: false:

const opts = {
  endpoint: 'wss://google.com',
  SocketConstructor: ws,
  reconnectInterval: 500,
  autoConnect: false
};

Have a look here about all the constructor parameters https://gregivy.github.io/simpleddp/simpleDDP.html, there is also autoReconnect.

from simpleddp.

Concerning the maxTimeout it is only for method calls.

from simpleddp.

Also don't forget that you have these events:

server.on('connected', () => {
    // do something
});

server.on('disconnected', () => {
    // for example show alert to user
});

server.on('error', (e) => {
    // global errors from server
});

from simpleddp.