(Sorry, just getting back to your messages in this thread.)

On 7/8/23 06:20, Graham Leggett wrote:
On 08 Jul 2023, at 10:08, Graham Leggett <>

Another data point - when starting the application up under tomcat9
in eclipse, there is also no mention in the logs of the web
application having been deployed, however I am able to hit the
application with curl and receive a sensible result. The
application has been silently started.

On the target machine, we get no log line same as under eclipse,
and no application (404 Not Found). The application might have been
silently started at a different URL and with no log line we’ll
never know, or it silently failed to start and with no error we’ll
never know.

Having switched from declaring a context in server.xml to
Catalina/localhost we now get the startup line - it seems that
applications defined in server.xml are silently deployed, but the
behaviour hasn’t changed, we still get 404 on the application.
Maybe this is what Konstantin meant when he said that server.xml-defined applications don't quite behave the same way.

08-Jul-2023 11:59:59.016 INFO [main]
org.apache.catalina.startup.HostConfig.deployDescriptor Deployment of
deployment descriptor
 has finished in [5,334] ms

Well, that's encouraging.

A further data point - the access_log as defined by default under the Host is 
created but stays empty:

       <Host name="localhost"  appBase="webapps"
             unpackWARs="false" autoDeploy="true" deployOnStartup="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" 
                prefix="localhost_access_log" suffix=".txt"
                pattern="%h %l %u %t &quot;%r&quot; %s %b" />


In summary, the client hits tomcat, tomcat returns 404 on the request, and 
there is no trace in the access logfile that the client was ever there.

Anyone seen behaviour like this before?

Absolutely stupid question: are you sure that the port number you are contacting to is being served by /this/ Tomcat process?


To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to