Hi Oliver,

Thank you for the snippet of server log you posted here.

In this snippet the NotificationException you mentioned in the first post of this thread is not present but there is a warning for a duplicate message (LS_msg_prog=3 for session ID Sc55170a060cdd7caT5329097).
In this case the most likely cause is that the client has lost, or received too late, the ack message sent from the server and re-sent the same message. This may highlight poor network conditions for the client.

Furthermore, from this log we do not notice the switching between http streaming and web socket connection for a specific client.
Indeed we count several sessions, some working with WebSocket (Sd23c4cc1bb096547T5107132 and Sb282503b4a33eaf0T0413676) and some others in HTTP Streaming (Sc55170a060cdd7caT5329097) but we can not figure out if they belong to the same client or are independent.

Please can you send us a wider snippet of the log where the life cycle of the clients involved is fully reported, at least since the creation of the session. (If you prefer you could send us the log via mail: support@lightstreamer.com).
Please can you confirm us that the NotificationException is not involved in the test case of the log you posted?

Thank you,
Giuseppe