Jump to content

SuperContainer Not Starting After FMS Upgrade to v22.0.1.66


Recommended Posts

Posted

Have just upgraded FMS on Windows Server 2022 Datacenter from FMS v20 to FMS v22. As with previous upgrades I have followed the instructions for adding the URL Rewrite Rule to IIS for the FMWebSite; when trying to access SuperContainer there's a 404 error.

 

I then reviewed the latest Catalina log file (FMS/Web Publishing/publishing-engine/jwpc-tomcat/logs and found three WARNING level entries:

[Server/Listener] failed to set property [AWTThreadProtection] to [True]

[Server/Service/Engine/Host/Context] failed to set property [className] to [org.apache.catalina.core.StandardContext]

The context path [/] has been changed to []

 

There are four SEVERE level entries:

org.apache.catalina.core.StandardContext.filterStart Exception starting filter [JSPModelFilter] (caused by java.lang.ClassNotFoundException: javax.servlet.Filter)

org.apache.catalina.core.StandardContext.filterStart Exception starting filter [UploadFilter] (caused by java.lang.ClassNotFoundException: javax.servlet.Filter)

org.apache.catalina.core.StandardContext.filterStart Exception starting filter [RegistrationFilter] (caused by java.lang.ClassNotFoundException: javax.servlet.Filter)

org.apache.catalina.core.StandardContext.filterStart Exception starting filter [LogFilter] (caused by java.lang.ClassNotFoundException: javax.servlet.Filter)

 

Because these filters failed to load, SuperContainer startup fails.

 

SC version is 2.9510 rev 13170 and it is installed in the FMS web publishing directory.

The Java version included with FMS (according to the release notes) is Temurin-17.0.7+7

 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.