In some situation after running for a long time (and I suppose, due to network problems), it is possible that calling a method of DDPClient results in an Error('not opened') being thrown by WebSocket.
This is what the exception looks like:
/usr/local/lib/node_modules/pi-steroid/node_modules/ddp/node_modules/ws/lib/WebSocket.js:175
else throw new Error('not opened');
^
Error: not opened
at WebSocket.send (/usr/local/lib/node_modules/pi-steroid/node_modules/ddp/node_modules/ws/lib/WebSocket.js:175:16)
at DDPClient._send (/usr/local/lib/node_modules/pi-steroid/node_modules/ddp/lib/ddp-client.js:77:15)
at DDPClient.call (/usr/local/lib/node_modules/pi-steroid/node_modules/ddp/lib/ddp-client.js:222:8)
This should be properly catched by DDPClient and transformed into a socket-error event (and a reconnection if automatic reconnection is enabled).
In some situation after running for a long time (and I suppose, due to network problems), it is possible that calling a method of DDPClient results in an Error('not opened') being thrown by WebSocket.
This is what the exception looks like:
This should be properly catched by DDPClient and transformed into a socket-error event (and a reconnection if automatic reconnection is enabled).