I meant servlet 3.0 async.
This is from CoyoteAdapter.java:
AsyncContextImpl asyncConImpl =
(AsyncContextImpl)request.getAsyncContext();
if (asyncConImpl != null) {
async = true;
} else if (!comet) {
response.finishResponse();
On 06/04/2011 20:50, Chris Dumoulin wrote:
> In looking into this further, it appears that the difference isn't in HTTP vs
> AJP, the difference is in async vs synchronous.
When you say asynchronous, do you mean Servlet 3.0 or Comet?
Mark
The logging now takes place in the CoyoteAdapter
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/connector/CoyoteAdapter.java?r1=1086351&r2=1086352&;
Filip
On 4/6/2011 2:26 PM, Filip Hanik - Dev Lists wrote:
Tomcat 6
http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/java/org/
2011/4/6 Chris Dumoulin :
> In looking into this further, it appears that the difference isn't in HTTP vs
> AJP, the difference is in async vs synchronous.
>
> The AJP traffic was carrying requests that were being processed
> asynchronously in Tomcat. If I switch to using the HTTP connector for t
Tomcat 6
http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/java/org/apache/catalina/valves/AccessLogValve.java?annotate=1030188
Look at the invoke() method, it logs the data
Tomcat 7
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/valves/AccessLogValve.java?view=annotate
Look
Just in case : have you looked at the 2 earlier [SECURITY] messages on this list, and at
the Change log for Tomcat 7.0.12 ? There are some notes there about asynchronous requests
that may have a bearing on your issue (maybe indirectly).
Chris Dumoulin wrote:
In looking into this further, it a
In looking into this further, it appears that the difference isn't in HTTP vs
AJP, the difference is in async vs synchronous.
The AJP traffic was carrying requests that were being processed asynchronously
in Tomcat. If I switch to using the HTTP connector for this same traffic I
still don't see
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 wr
Chris Dumoulin wrote:
I'm using tomcat 7.0.11 with the following Connector and Host elements in
server.xml:
In the access log I'm seeing the HTTP traffic on port 8080 but not the AJP
traffic on port 8009. I've googled around and I don't see any mention of
specific Valve s
I'm using tomcat 7.0.11 with the following Connector and Host elements in
server.xml:
In the access log I'm seeing the HTTP traffic on port 8080 but not the AJP
traffic on port 8009. I've googled around and I don't see any mention of
specific Valve settings for AJP.
Any id
10 matches
Mail list logo