Can anyone give a rough guess as to when Tomcat 7.0.13 will be released?
There's a fix in there that I'm looking forward to getting.
Thanks,
Chris
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional
Thanks for the info Mark!
On May 5, 2011 09:59:54 am Mark Thomas wrote:
On 05/05/2011 14:47, Chris Dumoulin wrote:
Can anyone give a rough guess as to when Tomcat 7.0.13 will be released?
There's a fix in there that I'm looking forward to getting.
Tomcat 7 releases around the start
Chris Dumoulin wrote:
In a discussion on Bug 50957
(https://issues.apache.org/bugzilla/show_bug.cgi?id=50957) Mark Thomas said
the following:
Experience has shown that most instances of this type of error are triggered
by
application bugs rather than Tomcat bugs - usually in the form
I'm seeing an intermittent problem with my webapp where a request is sent and
the response contains 8184 bytes from some other response followed by the
correct response.
The setup being used is Nginx 0.8.54 reverse proxying to Tomcat 7.0.11. AJP is
the protocol between Nginx and Tomcat.
The
information
disclosure] /may/ have something to do with this.
(It talks only about the HTTP connector, but also about content mixup with
async requests,
so maybe there is a link)
Chris Dumoulin wrote:
I'm seeing an intermittent problem with my webapp where a request is sent
to the outputStream?
- Writing to the output stream after it has been closed?
- Something else?
Thanks,
Chris
On April 13, 2011 07:31:45 am Chris Dumoulin wrote:
Actually, I saw that notice and tried Tomcat 7.0.12, but saw the same
behaviour. I should have mentioned that before.
So, I think
Thanks for your response Andre. I'm using AJP between Tomcat and Nginx using
this Nginx module: https://github.com/yaoweibin/nginx_ajp_module
There is definitely AJP traffic, it's just not showing up in the access log.
- Chris
On April 6, 2011 03:24:38 pm André Warnier wrote:
Chris Dumoulin
see anything in the access log. Other requests that are being
processed synchronously are showing up in the access logs.
I'm starting to step through the Tomcat code now, but any thoughts on this
would be appreciated.
- Chris
On April 6, 2011 03:31:18 pm Chris Dumoulin wrote:
Thanks for your
see logAccess() being called anywhere else, except in error cases.
So, it looks like the async case is missing a call to logAccess() somewhere.
- Chris
On April 6, 2011 04:44:27 pm Mark Thomas wrote:
On 06/04/2011 20:50, Chris Dumoulin wrote:
In looking into this further, it appears
Based on Mark Thomas' recommendation in another thread, I've upgraded to tomcat
7.0.11 and the issues I was seeing seem to be fixed.
This seems to be the relevant changelog entry:
Fix issues that prevented asynchronous servlets from working when used with
the HTTP APR connector on platforms
10 matches
Mail list logo