Scheduled Service Change: Maintenance, Restart Fedora Tomcat JVM
There is no workaround for this issue
The production Fedora Tomcat JVM needs to be restarted in order to load an updated XACML Policy file. The updated file will allow the Electronic Student Records webapp from CF9 to access the production Fedora server. During the approximately 90 second restart, services connecting to the Fedora server will fail and users will have a Sorry Page.