At a Glance

Released on
05/21/2014
End of Life
05/21/2015

Next Release: 7.12
Previous Release: 7.10.1

Cascade Server 7.10.2

Cascade Server version 7.10.2 improves the performance of index block caching in high concurrency environments and handles a regression bug introduced by 7.10.1 to the "Applicable to Groups" settings of destinations.

  View Requirements

Issues Resolved

  • [CSI-769] - Destinations: Applicable for Groups setting doesn't persist
  • [CSI-770] - CPU pegged at 100% due to multiple threads accessing HashSets in caching code; improved caching performance in high concurrency environments

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.

EhCache library changes on upgrades to 7.10.2 or later

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.

Database optimization on upgrades to 7.8.2 or later

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.

Rebuild search indexes on upgrade

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.

Warnings:

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

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