dario-weswit

Since the error may be caused by unexpected data received, it seems difficult to put a workaround by fixing the data. If anything, you could catch the exception, identify that...

Could you manage to extract something from the log file using some lightweight tool? For instance "grep -n" to find the error line and then "head" and "tail" to extract...

From Lightstreamer point of view, there is no explanation for this empty message. Since the message is read by a "readline", it should correspond to an empty line coming from...

Note that Lightstreamer Server has no strong requirement for shutdown. Although an ordered closure is better than a process and/or connections abrupt interruption, the clients should be able to cope...

@marcipops let me insist on the points expressed in my Jul 25 post. There is no need for an ordered shutdown of Lightstreamer Server. In any case, the python client...

@galburn there must be a misunderstanding. I think that your workaround should work. I didn't even notice it yesterday, when answering about Lightstreamer Server shutdown. My impression is that _read_from_stream...

With a browser client I would use a proxy, like fiddler, on which you can close sockets selectively. But I don't know if the Python runtime detects proxies seamlessly like...