Another options is to remove and deploy again using manager app. Just a
shortcut in case reload doesn't take care of new war (which I doubt is the
case).
Thanks
Avnish
- Original Message -
From: Liam Morley [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Tuesday, June 25,
Hi Everyone,
Recently I have connected apache with tomcat using mod_jk. In my httpd.conf
file I am giving this directive.
JkMount /examples/* ajp13
It works perfectly fine but problem is it forwards all requests to apache. I
want static requests to be handled by Apache.
As per documentation only
Hi Brendan,
with JkMount /*/servlet/* ajp13, debug files shows following lines. And maps
root (/) to tomcat which is not what I want :(
[jk_uri_worker_map.c (256)]: Into jk_uri_worker_map_t::uri_worker_map_open,
suffix rule /.jsp=ajp13 was added
[jk_uri_worker_map.c (267)]: Into
Brendan,
Thanks extending your help.
I can go with individual deployment, not a big problem (but still is a
problem isn't it). But just want to know when this isn't supported than why
the hell so many sites (I have seen more than 4-5 sites, one site setup J2EE
on windows and use ONLY these two
Hi All,
I am using apache 1.3.24 and tomcat 4.0.3 on win2k. I am using mod_jk for
communication between these two. My problem is while requesting anything
from tomcat thru apache, everything goes fine except some time images fails
to load within HTML pages. This is not very consistent problem but
You can run Tomcat alone if you are willing to serve static contents as well
from tomcat. But as tomcat documentation says, apache is more robust and
configurable when it comes to serving static contents. More over there are
lots of plugin modules available for apache which would be very useful
