https://bz.apache.org/bugzilla/show_bug.cgi?id=62028
Bug ID: 62028
Summary: Server Sent Event closed connection throws IOException
Product: Tomcat 9
Version: unspecified
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Component: WebSocket
Assignee: dev@tomcat.apache.org
Reporter: arturogarciamar...@gmail.com
Target Milestone: -----
Created attachment 35693
--> https://bz.apache.org/bugzilla/attachment.cgi?id=35693&action=edit
Tomcat 9 log, regarding Server Sent Events
Hi.
Dealing with Server Sent Events, by using Spring server-side, I've realized
that clients (JavaScript apps) do NOT send a "closing" signal for example when
user decides to change from one page to another.
This "human" behaviour leads to an "IllegalStateException" throwed by Tomcat
whenever Spring-based server-side app tries to communicate with the client,
because "it's a client app".
What seems to happen it that client side, the web app opens the connection, the
browser tells Tomcat to keep opened an asynchronous connection, the client and
the server apps keep talking, but, when the client app decides to "move", no
one tell neither Tomcat nor Spring to "close" the connection.
The next time the server app tries to send something to the client, the
connection does NOT EXIST! so... (see attached file)
Also, as you could see in the attached log file, there is another error raising
when Tomcat still keeps an asynchronous connection open and the Tomcat server
shuts down. This time is a NullPointerException, but also related with the same
origin.
I've been talking with Anne van Kesteren, from Mozilla ( see:
https://github.com/whatwg/html/issues/3380#issuecomment-359262402 ) but I have
got not a clear response...
Thanks all.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
