It used to work for a long time, but for some unknown reason it stopped. We reinstalled Apache and upgraded Tomcat to 7, looked at the configuration files, etc...
The big picture: - We have 4 workers
We use Netbeans
There is one connector on port 8080 (HTTP 1.1) and 4 AJP1.3 connectors
We also use Executors for connectors, no proxy
The platforms are as specified in the 'Title' above
"httpd DocumentRoot overlaps with a Tomcat Host's appBase or the docBase of any Context" not the case (http://tomcat.apache.org/connectors-doc/reference/apache.html)
If we direct the calls to "IP:8080/servlet" (therefore contacting Tomcat directly) everything is fine (i.e. servlets correctly contacted)
We eliminated the issue with connectors and IP's (i.e. all connectors responses to the same IP vs. each connector to a different IP) - setup insensitive, response the same
Looking at the 'Http Server Monitor' in Netbeans we see that all requests for servlets are correctly forwarded to Tomcat through various workers, however all requests are for port 80 of Tomcat. If we contact Tomcat directly (8080) we see in 'Http Server Monitor' the 'Port number of HTTP service) as being 8080 and servlets are activates properly, as indicated.
We use 'trace' for mod_jk log file and we can see that tomcat is connected and responds ("Service finished with status=404 for worker XXX").
Initially we thought that maybe mod_jk was corrupted somehow - it was replaced.
At this point in time we don't really know where to look - it seems like we are missing something, probably a setup ???.
Along these lines: we've noticed that each time a request is sent to Apache (let's say http://www.myserver.com), Apache will look at the mod_jk and try to find a match for all files included in the index.html (i.e. css, js, etc.), despite the fact that there is no pattern supplied. Probably an optimization will be in order.
We would appreciate if somebody can provide feedback.
server.xmlandmod_jk.log? – quanta Sep 9 '11 at 11:42