We patched/upgraded our Tomcat server from 8.5 to version 10 successfully on the UAT DU server.
Service started successfully. Login to Tomcat is fine. DU login on the server console is working. When we are trying to login to the URL: http://xx.xxx.x.xx:8080/univiewer
HTTP status 404 – Not Found Error.
Logging into the Tomcat manager, tried to start the application /univiewer. This comes up with the error.
Release : 6.10
Component : CA Automic Dollar Universe(AUTOMIC DOLLAR UNIVERSE)
The upgrade of Tomcat was made to version v10.0.12, whereas the supported version as per compatibility matrix is only v9.0.
The error in Tomcat logs while trying to deploy univiewer.war are below
16-Oct-2021 13:54:05.293 SEVERE [Catalina-utility-2] org.apache.catalina.core.StandardContext.startInternal Context [/univiewer] startup failed due to previous errors
16-Oct-2021 13:54:05.324 INFO [Catalina-utility-2] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive [C:\Program Files\Apache Software Foundation\Tomcat 10.0\webapps\univiewer.war] has finished in [36,731] ms
16-Oct-2021 13:54:05.293 SEVERE [Catalina-utility-2] org.apache.catalina.core.StandardContext.listenerStart Error configuring application listener of class [com.orsyp.servlet.filter.LoginFilter]
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at java.security.SecureClassLoader.defineClass(Unknown Source)
Above error reflect the issue related to incompatibility of DU 6.10 with Tomcat 10.x. The Tomcat 10.x, is based off Servlet API version 5.0 which in turn is part of Jakarta EE version 9. The javax.* package has been renamed to jakarta.* package since Jakarta EE version 9. This means that the deployed web application is actually not compatible with Jakarta EE version 9. The deployed web application is most likely developed for an older JEE version where the javax.* package is still used.
Follow the Compatibility Matrix and downgrade your Tomcat to supported version 9.0.