Replies: 1 comment
-
Hi @andrijan. Yes... these things can happen. Often there's a timeout somewhere, or something similar, that causes the connection to be closed (or, yes too, there can just be an error.) Folks have had success sending a heartbeat every so often, to make sure a connection isn't shut for being idle. All this depends on your provider… — I don't know if Heroku have any guidance on long-lived connections. It's not really something I can explicitly help you with though, I'm afraid. HTH |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey there!
I've been using
channels
in production for a while and everything works smoothly. Except when looking at the logs (or Sentry) I see some randomConnectionError
in my consumers.So my question is basically, are these
ConnectionError
s normal, due to network connectivity issues from the users?And if so, should I just ignore them (With a
try
/except
block)?If not, is there anything I should be doing differently in the consumer or maybe some configuration issue?
I'm using
daphne
and it is running on HerokuBeta Was this translation helpful? Give feedback.
All reactions