Author: markt
Date: Tue Mar 7 08:24:59 2017
New Revision: 1785810
URL: http://svn.apache.org/viewvc?rev=1785810&view=rev
Log:
Fix failing test
Modified:
tomcat/tc7.0.x/trunk/test/org/apache/catalina/core/TestAsyncContextImpl.java
Modified:
tomcat/tc7.0.x/trunk/test/org/apache/catalina/core
The Buildbot has detected a restored build on builder tomcat-7-trunk while
building . Full details are available at:
https://ci.apache.org/builders/tomcat-7-trunk/builds/687
Buildbot URL: https://ci.apache.org/
Buildslave for this Build: silvanus_ubuntu
Build Reason: The AnyBranchScheduler
tmp-APR
-Djunit.jar=/srv/gump/public/workspace/junit/target/junit-4.13-SNAPSHOT.jar
-Dobjenesis.jar=/srv/gump/public/workspace/objenesis/main/target/objenesis-2.6-SNAPSHOT.jar
-Dexamples.sources.skip=true
-Dcommons-daemon.jar=/srv/gump/public/workspace/apache-commons/daemon/dist/commons
tmp-NIO
-Djunit.jar=/srv/gump/public/workspace/junit/target/junit-4.13-SNAPSHOT.jar
-Dobjenesis.jar=/srv/gump/public/workspace/objenesis/main/target/objenesis-2.6-SNAPSHOT.jar
-Dexamples.sources.skip=true
-Dcommons-daemon.jar=/srv/gump/public/workspace/apache-commons/daemon/dist/commons
Author: remm
Date: Tue Mar 7 10:24:38 2017
New Revision: 1785820
URL: http://svn.apache.org/viewvc?rev=1785820&view=rev
Log:
Unlock a blocking read (with an IOE) when a stream exception occurs. The likely
bad behavior is seen in many tests in the testsuite. Originally I think this is
supposed t
Author: remm
Date: Tue Mar 7 10:24:53 2017
New Revision: 1785821
URL: http://svn.apache.org/viewvc?rev=1785821&view=rev
Log:
Unlock a blocking read (with an IOE) when a stream exception occurs. The likely
bad behavior is seen in many tests in the testsuite. Originally I think this is
supposed t
Author: markt
Date: Tue Mar 7 10:51:55 2017
New Revision: 1785823
URL: http://svn.apache.org/viewvc?rev=1785823&view=rev
Log:
Follow up to the fix for bug 58178. When creating the ELContext for a tag file,
ensure that any registered ELContextListeners are fired.
Added:
tomcat/trunk/test/web
Author: markt
Date: Tue Mar 7 10:53:59 2017
New Revision: 1785826
URL: http://svn.apache.org/viewvc?rev=1785826&view=rev
Log:
Follow up to the fix for bug 58178. When creating the ELContext for a tag file,
ensure that any registered ELContextListeners are fired.
Added:
tomcat/tc8.5.x/trunk/
Author: markt
Date: Tue Mar 7 10:56:10 2017
New Revision: 1785827
URL: http://svn.apache.org/viewvc?rev=1785827&view=rev
Log:
Follow up to the fix for bug 58178. When creating the ELContext for a tag file,
ensure that any registered ELContextListeners are fired.
Added:
tomcat/tc8.0.x/trunk/
https://bz.apache.org/bugzilla/show_bug.cgi?id=58178
--- Comment #7 from Mark Thomas ---
See also http://tomcat.markmail.org/thread/cnqkckysilwhpyip for a discussion on
a follow-up issue and r1785823, r1785826 and r1785827
--
You are receiving this mail because:
You are the assignee for the bug
The Buildbot has detected a new failure on builder tomcat-8-trunk while
building . Full details are available at:
https://ci.apache.org/builders/tomcat-8-trunk/builds/943
Buildbot URL: https://ci.apache.org/
Buildslave for this Build: silvanus_ubuntu
Build Reason: The AnyBranchScheduler sch
2017-03-07 11:24 GMT+01:00 :
> Author: remm
> Date: Tue Mar 7 10:24:38 2017
> New Revision: 1785820
>
> URL: http://svn.apache.org/viewvc?rev=1785820&view=rev
> Log:
> Unlock a blocking read (with an IOE) when a stream exception occurs. The
> likely bad behavior is seen in many tests in the tests
Author: remm
Date: Tue Mar 7 12:13:42 2017
New Revision: 1785832
URL: http://svn.apache.org/viewvc?rev=1785832&view=rev
Log:
Revert patch: the fix doesn't work if running more than one test (tested with
http2.TestHttp2Section_6_9).
Modified:
tomcat/trunk/java/org/apache/coyote/http2/Stream.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60828
Bug ID: 60828
Summary: After update - injected objects are not being
initialized
Product: Tomcat 7
Version: 7.0.75
Hardware: PC
Status: NEW
Severity
https://bz.apache.org/bugzilla/show_bug.cgi?id=60828
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On 07/03/17 11:48, Rémy Maucherat wrote:
> 2017-03-07 11:24 GMT+01:00 :
>
>> Author: remm
>> Date: Tue Mar 7 10:24:38 2017
>> New Revision: 1785820
>>
>> URL: http://svn.apache.org/viewvc?rev=1785820&view=rev
>> Log:
>> Unlock a blocking read (with an IOE) when a stream exception occurs. The
>> l
https://bz.apache.org/bugzilla/show_bug.cgi?id=57665
--- Comment #6 from Christopher Schultz ---
(In reply to Balasubramanian from comment #5)
> In which version of tomcat, this fix is available? I did not see this fix in
> tomcat 9 and 8.
What led you to believe that this enhancement request an
https://bz.apache.org/bugzilla/show_bug.cgi?id=57665
--- Comment #7 from Christopher Schultz ---
I'm curious why this enhancement has even been requested. My understanding of
the HTTP spec is that the "Host" header should not be modified by an
intervening reverse-proxy.
https://www.w3.org/Protoc
https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
--- Comment #13 from Christopher Schultz ---
(In reply to Ty from comment #12)
> - there is no OOME in stdout or stderr
I seem to recall some try/catch code in certain places in Tomcat that swallowed
exceptions that I thought ought to at least
https://bz.apache.org/bugzilla/show_bug.cgi?id=57665
--- Comment #8 from Mike Youngstrom ---
We modify the Host header mostly to work around limitations in application
platforms our apps are hosted on.
For example, Cloud Foundry only recently added support for path based routing
and even still i
https://bz.apache.org/bugzilla/show_bug.cgi?id=57665
--- Comment #9 from Stefan Fussenegger ---
There are other scenarios than "an intervening reverse-proxy". One example
would be a CDN that use the Host header of the backend and adds the original
value as X-Forwarded-Host. (e.g. "Host: origin.ex
https://bz.apache.org/bugzilla/show_bug.cgi?id=57665
Christopher Schultz changed:
What|Removed |Added
Attachment #33985|0 |1
is patch|
https://bz.apache.org/bugzilla/show_bug.cgi?id=57665
--- Comment #10 from Christopher Schultz ---
Okay. I have no particular objection to this patch.. I just wanted to
understand the use-cases a little more.
--
You are receiving this mail because:
You are the assignee for the bug.
-
https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
--- Comment #14 from Ty ---
> OOMEs can happen for a number of reasons -- not always complete
> heap-exhaustion.
Very true, I forgot about the "initialize an object array of
size=Integer.MAX_VALUE" operations that OOME before they even begin.
Author: markt
Date: Tue Mar 7 21:56:10 2017
New Revision: 1785893
URL: http://svn.apache.org/viewvc?rev=1785893&view=rev
Log:
Add test case to explore issue reported on users list.
Added:
tomcat/trunk/test/org/apache/tomcat/websocket/server/TestAsyncMessages.java
Added:
tomcat/trunk/test/o
Author: markt
Date: Tue Mar 7 21:59:21 2017
New Revision: 1785895
URL: http://svn.apache.org/viewvc?rev=1785895&view=rev
Log:
Add supporting class
Added:
tomcat/trunk/test/org/apache/tomcat/websocket/TesterAsyncTiming.java
Added: tomcat/trunk/test/org/apache/tomcat/websocket/TesterAsyncTimi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
If I stop a Connector (e.g. using JMX), I know that the listen port
will be unbound and new connections will fail. But what about
in-process requests?
My testing shows that with a simple JSP like this:
<% Thread.sleep(10 * 1000); %>This is a
https://bz.apache.org/bugzilla/show_bug.cgi?id=57830
--- Comment #16 from Axel U ---
Is there an update on adding PROXY protocol support?
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscrib
28 matches
Mail list logo
