Apache Tomcat V9.0.62 Download
Mathilda Haakinson
To access page.jsp url I type: website.com/folder1/page.jspThis all works as expected in localhost on any tomcat version, however when I deploy it to azure app service Tomcat v9.0.62 page.jsp is mapped to root: website.com/page.jspIf I downgrade to tomcat v9.0.54 it works as expected.I'd really appreciate any help in figuring out how to fix this behavior when deployed
cp activemq-all-5.7.0.jar commons-beanutils-1.7.0.jar commons-beanutils-core-1.8.0.jar commons-collections-3.2.1.jar commons-configuration-1.6.jar commons-digester-1.8.jar commons-lang-2.4.jar commons-logging-1.1.1.jar ecj-4.4.2.jar exlibris-jasypt-encryption-1.0.3.jar icu4j-3.8.1.jar jasypt-1.9.0.jar ojdbc8-12.2.0.1.jar tomcat7-websocket.jar ../../search/lib/
From the top of my head, I thought Eclipse started the tomcat server without anything in it, i.e. no web applications. You have to 'run' or actually deploy something in that Eclipse Tomcat server so you won't get the 404s.
I had the same problem, which was solved when I changed the admin port (right-click on the server inside eclipse and select properties) from a hyphen(default) to another port number. I used another port number for the admin port (not the same as the port number I used for my tomcat)
You will want to add a user who can access the manager-gui and admin-gui (web apps that come with Tomcat). You can do so by defining a user, similar to the example below, between the tomcat-users tags. Be sure to change the username and password to something secure:
So here now is the full tomcat logs after a restart until nothing happens anymore without XWiki being accessible (of course strippend by some intermediate stacktrace lines): Errornous XWiki tomcat logs - Paste-bin for Sharing Code and Text
Simplified generation of portable build native binaries, a simple mvn clean install -Dgenerate-native-launchers=true
is all that is needed to generate the binaries. As this takes some more time, is only needed when upgrading tomcat and
needs to download artifacts not present on Maven's central repo, it is not enabled by default.