You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2015/03/24 12:44:04 UTC
[Bug 57750] New: WebSocket does not get closed when network is
disconnected
https://bz.apache.org/bugzilla/show_bug.cgi?id=57750
Bug ID: 57750
Summary: WebSocket does not get closed when network is
disconnected
Product: Tomcat 7
Version: 7.0.50
Hardware: PC
OS: Linux
Status: NEW
Severity: major
Priority: P2
Component: Catalina
Assignee: dev@tomcat.apache.org
Reporter: roman.stobnicki@dialogic.com
We created a WebSocket between a browser (Chrome) and Mobicents ApacheTomcat
Application Server. When network gets disconnected we expected to for our
onClose() method to be called at some point now that the connection has been
compromised. In the meantime we are going to implement ping-pong type of
messaging but since WebSocket rides on TCP and it has its keep alive mechanism
already there should be no need to do anything outside of it. Please advise and
let me know if you need any additional information.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 57750] WebSocket does not get closed when network is
disconnected
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=57750
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Status|NEW |RESOLVED
--- Comment #3 from Mark Thomas <ma...@apache.org> ---
Thanks Chris. I hadn't joined up those dots.
*** This bug has been marked as a duplicate of bug 57546 ***
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 57750] WebSocket does not get closed when network is
disconnected
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=57750
--- Comment #1 from Mark Thomas <ma...@apache.org> ---
Which WebSocket implementation?
Which connector?
Depending on circumstances, Tomcat may not be informed of the network
disconnection - in which case there is no way for Tomcat to call onClose().
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 57750] WebSocket does not get closed when network is
disconnected
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=57750
--- Comment #5 from roman.stobnicki@dialogic.com ---
Sorry for late replay but update emails were caught in my spam :-)
Just wanted to add that actually we did many tests and found out that TCP keep
alive timers are only good between the "hops" and not end to end. So,
implementing some sort of Ping/Pong mechanism one level higher seems to be the
only way to verify if the two ends can still talk to each other or not.
The test: I have connected a Chrome client running on a laptop and called into
my conferencing application running on ApacheTomcat. When connection was
established after about 40 seconds I disconnected the network on the laptop and
noticed that websocket was not notified that it was closed. If I attempted to
send something to it at that moment then it will tell me that websocket no
longer exists. Changing TCP keepalive timers on AS I could see them going back
and forth from AS out and back... but did not see them on the client machine at
all. That is what made me believe that these timer settings are only between
the network hops.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 57750] WebSocket does not get closed when network is
disconnected
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=57750
--- Comment #4 from Christopher Schultz <ch...@christopherschultz.net> ---
(In reply to Mark Thomas from comment #3)
> Thanks Chris. I hadn't joined up those dots.
>
> *** This bug has been marked as a duplicate of bug 57546 ***
FTR, bug #57546 was fixed in 7.0.59. Please upgrade and re-test.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
[Bug 57750] WebSocket does not get closed when network is
disconnected
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=57750
--- Comment #2 from Christopher Schultz <ch...@christopherschultz.net> ---
I seem to recall markt doing some work on this recently: you (Mark) weren't
able to replicate a network drop by disconnecting your VMs network, but
physically pulling the Ethernet cable from your laptop seemed to do the trick.
Could this have been fixed /post/ 7.0.50?
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org