tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Thomas <>
Subject Re: svn commit: r1530081 - /tomcat/trunk/java/org/apache/tomcat/util/net/
Date Tue, 08 Oct 2013 13:56:47 GMT
On 08/10/2013 14:50, Konstantin Prei├čer wrote:
> Hi Mark,
>> -----Original Message-----
>> From: []
>> Sent: Monday, October 7, 2013 11:44 PM
>> To:
>> Subject: svn commit: r1530081 -
>> /tomcat/trunk/java/org/apache/tomcat/util/net/
>> Author: markt
>> Date: Mon Oct  7 21:44:09 2013
>> New Revision: 1530081
>> URL:
>> Log:
>> Fix for APR.
>> If the socket was registered for read and write and only one occurred, the
>> registration for the other event was lost. Ensure that the socket is re-
>> registered with the Poller when necessary.
> Thanks for the fix.
> Unfortunately, for APR it seems there is an issue with connections being closed by Tomcat
(on Windows):
> After resuming firefox.exe, in ~ 50% of the cases Tomcat will close the connection one
second after resuming the browser (which normally shouldn't happen). The snake will disappear
in the other browser and Firefox prints "WebSocket cosed".
> Any idea about this?

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.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message