At a Glance

Released on
End of Life

Next Release: 7.12.4
Previous Release: 7.12.2

Cascade Server 7.12.3

Cascade Server version 7.12.3 contains improvements to access checks as well as a system health monitoring tool. A new link checking preference has also been added which allows administrators to disable external link checks during publishing. A handful of other bugs have also been addressed.

  View Requirements

Speeding Up Access Checks

On any screen in the system, many access checks must be performed to determine whether or not the current user can see certain assets or links to those assets.  As more assets and users are added to the system, these checks can lead to performance degradation.  In Cascade 7.12.3, we have taken steps to cut down on the amount of time that is dedicated to doing these access checks.  This improves the responsiveness of the application in general but also improves things like page rendering times and load times of certain dashboard widgets.

System Health Monitoring

Included in Cascade 7.12.3 is a performance monitoring tool called Java Melody.  This tool allows adminstrators to keep a close eye on many key system performance metrics in the system.  These include memory statistics, page load statistic, database query statistics and more.  See the support knowledgebase for instructions on how to enable Java Melody.

Long Publish Times Due to External Link Checking

With the release of the Broken Link Report in Cascade 7.12, external link checking was added during publishing to make link checking consistent everywhere: on publish, on submit, and during the broken link report. This had the side effect of increasing publish times -- minimally in most cases but dramatically in others.

7.12.3 adds a new preference for both the Global area and individual Sites that allows site managers to set whether or not external links should be checked during publish. By default, this preference is set to not check external links on publish. Users can then rely on the Broken Link Report for external link checks.

In a future release, we will introduce a new external link checking system that reduces the impact of external link checking during publishing substantially.

New Features

  • [CSI-763] - Improve access checking performance
  • [CSI-830] - Integrate System Health Monitoring Tool: Java Melody


  • [CSI-828] - Reduce memory usage while loading stale content tab and widget

Issues Resolved

  • [CSI-803] - Columns in cxml_site are too short in sql server
  • [CSI-808] - It is possible to save a draft of a working copy
  • [CSI-809] - Asset Submit button incorrect when toggling off 'start workflow' and using browser's back button
  • [CSI-815] - Asset local links no longer work
  • [CSI-816] - Disable Page XML/Block XML options when Regular Content is unchecked in Index Block edit
  • [CSI-818] - Disabling: "Enable Automatic Synchronization" in LDAP configuration and submitting doesn't unschedule LDAP sync
  • [CSI-819] - Embedded Images not rendering in PDFs
  • [CSI-826] - Broken Link Report errors due to Java 7 SSL Error 'handshake alert: unrecognized_name'
  • [CSI-827] - Long publish times for instances with lots of slow and/or broken external links

First Time Installation?

Be sure to import our default database schema prior to installing Cascade Server for the first time. Then follow our standard installation instructions.

Upgrade Steps

  1. Shut down your currently running Cascade Server instance.
  2. Before you upgrade, we strongly recommend that you back-up your production database. as well as set up a test instance and perform a trial run of the upgrade. All customers are entitled to a test license for this purpose.
  3. Read the release notes and upgrade guides for all releases between your version and the latest version.
  4. If your current version of Cascade is earlier than 7.0, then you must use the full installation instructions.
  5. If your current version of Cascade is 7.0 or later, you can perform a full installation or upgrade in place using the ROOT.war installation.
  6. Certain versions require that specific steps be taken during the upgrade process. Be sure to read over any and all items that apply to the version to which you are upgrading:

Organizations that use the ROOT.war upgrade method and are upgrading to 7.12.3 or later must follow these steps:

  • If running in a load balanced environment, check to see if the file tomcat/conf/ehcache.xml exists on each node. If this file exists, please contact support [at] prior to performing the upgrade. If the file does not exist, proceed with the upgrade as usual.
  • If not running in a load balanced environment, remove the file tomcat/conf/ehcache.xml prior to performing the upgrade.

Organizations that use the ROOT.war upgrade method and are upgrading from 7.12.1 or earlier to 7.12.2 or later and use MySQL 5.6 must manually update the driver library in tomcat/lib folder from mysql-connector-java-5.1.18-bin.jar to mysql-connector-java-5.1.31-bin.jar. The file mysql-connector-java-5.1.31-bin.jar can be obtained by downloading ZIP version of Cascade Server.

Organizations that use the ROOT.war upgrade method and are upgrading from 7.10.1 or earlier to 7.10.2 or later must remove the ehcache-core-*.jar and slf4j-api-*.jar from the ${CATALINA_BASE}/lib of Tomcat.

Organizations upgrading to 7.8.2 or above for the first time may notice a delay during the initial startup accompanied by messages like these in the log file:

2014-01-01 11:53:25,405 INFO  [OptimizeDatabaseServiceImpl] Clearing orphaned assets...
2014-01-01 11:53:25,405 INFO  [OptimizeDatabaseServiceImpl] Clearing orphaned Data Definition nodes...
2014-01-01 11:54:09,508 INFO  [OptimizeDatabaseServiceImpl] Deleted 7 orhpaned Data Definition nodes
2014-01-01 11:54:09,508 INFO  [OptimizeDatabaseServiceImpl] Repeating the operation until there are no more orhaned nodes to delete
2014-01-01 11:54:57,350 INFO  [OptimizeDatabaseServiceImpl] Deleted 14 more orhpaned Data Definition nodes
2014-01-01 12:02:30,529 INFO  [OptimizeDatabaseServiceImpl] Repeating the operation until there are no more orhaned nodes to delete
2014-01-01 12:02:58,724 INFO  [OptimizeDatabaseServiceImpl] Deleted 0 more orhpaned Data Definition nodes
2014-01-01 12:02:58,725 INFO  [OptimizeDatabaseServiceImpl] Finished clearing 224 orphaned Data Definition node record(s)
2014-01-01 12:02:58,725 INFO  [OptimizeDatabaseServiceImpl] Fixing Structured Data with missing owner entity property
2014-01-01 12:03:29,712 INFO  [OptimizeDatabaseServiceImpl] Found 211 broken Structured Data nodes
2014-01-01 12:03:32,451 INFO  [OptimizeDatabaseServiceImpl] Fixed a total of 9 assets with broken Structured Data nodes
It is important that the Cascade Server process not be stopped during this time. Once the orphaned Data Definition nodes have been removed, the application will start up normally.

If you are upgrading from Cascade Server 7.4.1 or later, you should rebuild search indexes after the upgrade is complete and the application is running. To do so, navigate to System Menu -> Utilities -> Search Indexing, check the Rebuild Index? checkbox and then click Submit.


You must upgrade to at least Cascade Server 5.5 before upgrading to Cascade 6 or Cascade 7.

Contact Hannon Hill Support ( if deploying Cascade Server for the first time in a load-balanced environment as this will require a special license.