When a long lived web socket client is used it is common for the connection to be lost and then re-established. While the connection is lost the event stream gets blocked. As soon as the client re-connects, the stream is unblocked. It has been observed however that every once in a while event streams remain blocked even after the client re-connects. So far the only work around that appear to take it out of that state is restarting ethconnect.
When a long lived web socket client is used it is common for the connection to be lost and then re-established. While the connection is lost the event stream gets blocked. As soon as the client re-connects, the stream is unblocked. It has been observed however that every once in a while event streams remain blocked even after the client re-connects. So far the only work around that appear to take it out of that state is restarting ethconnect.