On 21/10/2015 15:31, Rémy Maucherat wrote: > 2015-10-21 16:14 GMT+02:00 Mark Thomas <ma...@apache.org>: > >> On 20/10/2015 15:30, Mark Thomas wrote: >> >>> I found the root cause of the Gump failure. It was an error in the >>> refactoring when I switched WebSocket from Servlet 3.1 non-blockin I/O >>> to goting directly to Tomcat's I/O layer. >>> >>> I'll take a look at NIO2/Chrome next. >> >> Sorry, I still haven't got to this. I was distracted by finding that the >> non-blocking I/O examples were failing for HTTP/2. >> >> Having fixed those bugs, are your NIO2/Chrome issues any better? >> > Yes, it still looks the same. For some reason some timeouts occur although > it looks fairly certain the server didn't receive anything or misprocessed > some input [or output since it's fairly certain the encryption and IO work > well enough for static files].
Drat. I thought those fixes might help. Oh well. I plan to start the 1.2.0 tc-native release next and then look at this while that vote runs. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
