When using Tomcat version 8.5.45 or greater and RMS 4.6.13, RMS does not work.  The odd thing is that Tomcat runs just fine, it starts, you can get to the base Tomcat page, but going to the RMS page only returns a 404 error.  The only sign of an issue is a ‘partial’ error message in the Tomcat stderr log.  Here’s what it looks like:

               at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:719)

               at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:714)

               at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:970)

               at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1841)

               at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

               at java.base/java.util.concurrent.FutureTask.run(Unknown Source)

               at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

               at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

               at java.base/java.lang.Thread.run(Unknown Source)

You can never get the full error to print out, even if you run Tomcat in Debug mode, but this is the closest you get to either program telling you there is a problem.  The error appears after the Starting ProtocolHandler message in the logs.  The RMS log doesn’t even get a chance to start, so it is empty.

Every version of Tomcat 8.5 has been tested, and this is the only version that fails (at the time of this writing it is also the most recent).  The release before this one, 8.5.43, works fine.