Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exception: Can't send data because WebSocket is not opened #30

Open
rentallect opened this issue Nov 16, 2020 · 0 comments
Open

Exception: Can't send data because WebSocket is not opened #30

rentallect opened this issue Nov 16, 2020 · 0 comments
Labels
bug Something isn't working

Comments

@rentallect
Copy link
Member

If a webapp is left idle over night, the websockets typically get closed. When the webapp attempt to send traffic the next day, we should just spin up a fresh channel to the edge router... but something currently goes awry, as shown here:

Uncaught (in promise) TypeError: Can't send data because WebSocket is not opened.
    at exports.throwIf (ziti.js:152980)
    at ZitiWebSocket.send (ziti.js:153687)
    at Object.tlsDataReady (ziti.js:132461)
    at Object.tls.flush (ziti.js:74391)
    at Object.c.prepare (ziti.js:75013)
    at ZitiTLSConnection.prepare (ziti.js:132527)
    at ZitiChannel._sendMarshaled (ziti.js:130366)
    at ziti.js:130292
    at PromiseController._callFn (ziti.js:119945)
    at PromiseController.call (ziti.js:119846)
    at Messages._createNewMessage (ziti.js:132134)
    at Messages.create (ziti.js:132106)
    at ZitiChannel.sendMessage (ziti.js:130291)
    at ziti.js:129984
@rentallect rentallect added the bug Something isn't working label Nov 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant