Author: markt
Date: Mon Feb 23 11:26:56 2015
New Revision: 1661642
URL: http://svn.apache.org/r1661642
Log:
Don't default to an infinite timeout for write. Generally, writes should happen
(fairly) quickly.
Modified:
tomcat/trunk/java/org/apache/coyote/http11/upgrade/UpgradeProcessor.java
2015-02-23 13:32 GMT+01:00 Mark Thomas ma...@apache.org:
I'm not sure if that is fixing the symptom or the cause. I'm still
seeing something going wrong with what should be a clean shutdown in
TestWsWebSocketContainer.testMaxMessageSize04().
I took a look at the source for
On 23/02/2015 13:24, Rémy Maucherat wrote:
2015-02-23 13:32 GMT+01:00 Mark Thomas ma...@apache.org:
I'm not sure if that is fixing the symptom or the cause. I'm still
seeing something going wrong with what should be a clean shutdown in
TestWsWebSocketContainer.testMaxMessageSize04().
I
On 23/02/2015 12:07, Rémy Maucherat wrote:
2015-02-23 12:26 GMT+01:00 ma...@apache.org:
Author: markt
Date: Mon Feb 23 11:26:56 2015
New Revision: 1661642
URL: http://svn.apache.org/r1661642
Log:
Don't default to an infinite timeout for write. Generally, writes should
happen (fairly)
2015-02-23 12:26 GMT+01:00 ma...@apache.org:
Author: markt
Date: Mon Feb 23 11:26:56 2015
New Revision: 1661642
URL: http://svn.apache.org/r1661642
Log:
Don't default to an infinite timeout for write. Generally, writes should
happen (fairly) quickly.
This is messing up some tests for
