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 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 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 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 wrote:
I'm using tomcat 7.0.11 with the following Connector and Host elements in
server.xml:
<Connector connectionTimeout="20000" port="8080" protocol="HTTP/1.1"
redirectPort="8443"/>
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/>
<Host appBase="webapps" autoDeploy="true" name="localhost" unpackWARs="true">
<Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" pattern="%h %l %u %t "%r"
%s %b" prefix="localhost_access_log." resolveHosts="false" suffix=".txt"/>
<Context docBase="app1" path="/app1" reloadable="true"
source="org.eclipse.jst.jee.server:app1"/>
<Context docBase="app2" path="/app2" reloadable="true"
source="org.eclipse.jst.j2ee.server:app2"/>
</Host>
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 ideas?
And are you expecting traffic on the AJP Connector ?
For traffic to show up there, some client would need to connect to your server on port
8009. Is there anything that connects to that port ?
If not, then there is nothing to worry about, and you could even comment-out that
<Connector>, since it will never be used.
Like :
<!-- Connector port="8009" protocol="AJP/1.3" redirectPort="8443"/ -->
The AJP Connector is used in scenarios where there is another webserver used as a
front-end to Tomcat, and this other webserver, to pass requests to Tomcat, uses the AJP
protocol. For example, a configuration like this one :
browser <--> Apache httpd server <-----> Tomcat
+ mod_jk module
OR + mod_proxy_ajp module
or
browser <--> IIS webserver <-----> Tomcat
+ isapi_redirect module
If you do not use such a configuration, or you do not understand what this is all about,
then you don't need the AJP <Connector> in Tomcat.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
