On 09/10/2013 02:41, Konstantin Preißer wrote:
> Mark,
> 
>>> -----Original Message----- From: Mark Thomas
>>> [mailto:ma...@apache.org] Sent: Tuesday, October 8, 2013 3:57 PM 
>>> To: Tomcat Developers List Subject: Re: svn commit: r1530081 - 
>>> /tomcat/trunk/java/org/apache/tomcat/util/net/AprEndpoint.java
>>> 
>>> 
>>> None. I've seem the same problem but haven't got to the bottom of
>>> it yet. What I do know is: - Tomcat doesn't send a close - The
>>> browser closes the connection on its own - Tomcat tries (and
>>> fails) to write some data and that triggers the close on the
>>> Tomcat side
>>> 
>>> I'm wondering if some form of data corruption could be the
>>> trigger.
>>> 
>>> Whatever is going on, I'm fairly sure it is a different issue to
>>> BZ 55633.
>>> 
>>> I need to do some more careful analysis with Wireshark.
>> 
>> OK, thanks.
>> 
>> Note: When I tested this scenario, I got a slightly other result:
>> For me, Tomcat initiated the shutdown of TCP connection. (And
>> another issue: When/After this happens, if the browser tries to
>> establishes a new Websocket connection (with a Upgrade: ... header)
>> then tomcat sometimes shuts down the TCP connection without sending
>> a reply).
> 
> I do now see the behavior which you described, but with the NIO
> connector: There the browser is the one which closes the connection
> (probably due to a data corruption).

With the current 8.0.x code, I can no longer recreate this issue (I am
using Firefox and Chrome) with NIO and have been pausing Chrome.

I also tried suspending Firefox and could not re-create the issue.

> When trying with APR, I keep seeing that Tomcat initates the
> connection shutdown.

I do still see the error when using APR with the current code. I'll dig
into this some more.

> With BIO, the problems don't occur.


Note that if you suspend for too long, you may hit the default write
timeout (20s) and that may trigger a connection close.

Mark

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

Reply via email to