It turns out that I was premature in concluding connections were
silently getting dropped.
I left the client application running for another quarter hour after it
stopped displaying message updates from the server. On shutting it
down, the server immediately recorded that the client had just
disconnected. This indicates that the WebSocket connection is not being
silently dropped afterall, rather the client is becoming deaf to inbound
messages after a few minutes.
Exactly why this is is a mystery. But evidently it is a Tyrus rather
than a Tomcat or network issue (they communicate across the internet, to
answer your earlier question).
Regards,
Chris.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
