Hi all,

I have for a while now been moving various web applications onto a new machine 
running tomcat9, and things have been working great. I have suddenly reached 
one web application which is silently ignored.

Tomcat starts up without any error, makes no mention of the webapp. If the 
webapp points to a bogus directory, tomcat complains very loudly, point tomcat 
to the correct directory, tomcat ignores the webapp.

Any attempt to hit the webapp returns the dreaded tomcat 404 page. 
Interestingly hitting /foo/bar returns a redirect to /foo/bar/ (as you would 
expect it to), but /foo/bar/ returns a tomcat 404.

The webapp is not being newly developed, and works fine on tomcat7 on the old 
machine.

Is there anything that can be done to coax an error message or any message out 
of tomcat when it fails to deploy something?

Snip of server.xml looks like this:

      <Host name="localhost"  appBase="webapps"
            unpackWARs="true" autoDeploy="true">

        <!-- SingleSignOn valve, share authentication between web applications
             Documentation at: /docs/config/valve.html -->
        <!--
        <Valve className="org.apache.catalina.authenticator.SingleSignOn" />
        -->

        <!-- Access log processes all example.
             Documentation at: /docs/config/valve.html
             Note: The pattern used is equivalent to using pattern="common" -->
        <Valve className="org.apache.catalina.valves.AccessLogValve" 
directory="logs"
               prefix="localhost_access_log" suffix=".txt"
               pattern="%h %l %u %t &quot;%r&quot; %s %b" />

        <Context path=“/foo/bar" docBase="/usr/share/foo-bar">

        </Context>
      </Host>

Regards,
Graham
—


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to