Hi Charles, thanks for the quick response.
#1: When I take Apache out of the picture, it behaves as expected:
Accessing an undeployed app through tomcat gives 404, and changes are
picked up when I re-deploy. Unfortunately, running it through Jk still
shows the very original version.
#2: There is only one <Context> tag pointing directly at the webapp, and
that's in server.xml
#3: I did a "find" over the whole system, and there's only one class
file for the compiled JSP.
Might this have something to do with the fact I'm running this through
virtual hosts on both apache and tomcat?
in Apache's http.conf, I have:
LoadModule jk_module libexec/mod_jk.so
JkWorkersFile "etc/workers.properties"
JkMount /*.jsp ajp13
<VirtualHost *:80>
ServerName virtual.xxx
DocumentRoow /disk2/vwww/virtual.xxx/htdocs
</VirtualHost>
And in Tomcat's server.xml, I have:
<Engine name="Catalina" defaultHost="localhost">
....
<!-- note: changing enableLookups to true didn't fix it -->
<Connector port="8009" enableLookups="false"
redirectPort="8443" protocol="AJP/1.3" />
<Host name='virtual.xxx' debug='0'
appbase='/disk2/tomcat/current/webapps/virtual.xxx'
autoDeploy='true' unpackWARs='true'>
<!-- this is the only Context line in the whole file -->
<Context path='' docBase='webapps/virtual.xxx'
debug='0' />
</Host>
</Engine>
Cheers,
-Darren
Caldarale, Charles R wrote:
A few things to try:
1) Take httpd out of the picture, just to make things simpler. Test
using Tomcat's http port (usually 8080). Once you find and fix the
problem, verify that operation through Apache is also corrected.
2) Look around for a <Context> tag for your webapp that has a docBase
attribute pointing to somewhere other than Tomcat's webapps directory.
This can be in META-INF/context.xml in the app's .war file or directory,
in conf/Catalina/<host_name>/<app_name>.xml, or in conf/server.xml
(which shouldn't be used these days). Your app may be getting deployed
multiple times under different names if there's more than one <Context>
tag for it.
3) Look around for the compiled JSP class, and get rid of it if found.
Your undeploy mechanism should have done this for you. (What are you
using to undeploy?)
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
