Hi Mark,

> -----Original Message-----
> From: Mark Thomas [mailto:ma...@apache.org]
> Sent: Thursday, October 10, 2013 5:22 PM

> I still can't reproduce this. I have Tomcat running in a VM with the
> bandwidth limited to 192Kbps and two separate machines accessing the
> drawing board. Can you try to reproduce this without the TCP forwarder
> in the mix just to make sure there isn't an issue there?
> 
> I do see the odd stray connection but it looks to be something the
> browser is holding on to. As soon as I close the browser, the connection
> drops.

Yes, I reproduced the issue without the TCP forwarder (Firefox connecting 
directly to Tomcat).

I just tried it again, and it seems the issue is somewhat hard to reproduce - I 
had to try this (Pressing F5) several minutes until the problems showed up 
again (the NPE in NioEndpoint.processSocket(), Firefox is unable to make a new 
HTTP request to Tomcat, and Tomcat closed an existing WebSocket connection from 
the other machine).

After this happens, then when I close all browsers on every machine and open 
new instances to make new HTTP requests (with IE, Chrome and Firefox), then 
sometimes Tomcat replies, but sometimes not.


Regards,
Konstantin Preißer


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to