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].
Rémy
