Tomcat fails when Thingworx webapp installed

Forum|Forum|8 years ago
July 24, 2017
1 reply
5170 views

I'm following the guide for RHEL. I installed Tomcat 8.5.16 since I couldn't find the noted version. Tomcat works fine and can be accessed at localhost:8080. As soon as I add the Thingworx webapp it can no longer be accessed. Interestingly, if I remove Thingworx.war and the xploded folder while tomcat is still running it I will be able to access the Tomcat welcome page again. No need to restart.

Install-Upgrade

S

supandey

5-Regular Member

Hi Anthony, could you check the error in the tomcat log when you are attempting to deploy the ThingWorx war? Which version of ThingWorx are you attempting to install and with which persistence provider?

A

amandra

Author

1-Visitor

Foundation server 7.4 trial

localhost log:

25-Jul-2017 08:46:00.258 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log No Spring WebApplicationInitializer types detected on classspath

catalina:

25-Jul-2017 08:50:00.084 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [/usr/tomcat/webapps/Thingworx.war]

25-Jul-2017 08:50:03.944 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.