At a Glance

Released on
12/12/2014
End of Life
12/12/2015

Next Release: 7.12.5
Previous Release: 7.12.3

Cascade Server 7.12.4

Cascade Server version 7.12.4 contains a fix for an inconsistency introduced in 7.12.3 with the way certain Velocity functions handle NULL parameters.

  View Requirements

7.12.3 Users

If you are using 7.12.3, it is recommended that you upgrade to 7.12.4 to fix an issue with Velocity introduced in 7.12.3

NULL values in Velocity function parameters

7.12.3 introduced a change to the way null parameters were handled when using the $_XPathTool. Specifically, relative XPath expressions applied to null contexts started throwing exceptions where before they would simply return null.

Here's an example:

#set ($param = ... some expression that results in NULL ... )
#set ($node = $_XPathTool.selectSingleNode($param, 
"something"))

In 7.12.2, $node would evaluate to to NULL because the passed $param was NULL. 7.12.3 changed this behavior to start throwing page-level render errors alerting users to the NULL context being passed to the selectSingleNode function.

This change only affected relative XPath expressions. Absolute node references e.g. /path/to/something would throw exceptions in both versions.

7.12.4 restores the functionality from 7.12.2 as some implementations were relying on $node evaluating to NULL and not erroring out.

Issues resolved

  • [CSI-836] - Exceptions thrown with Velocity scripts that used to work due to change in null-checking

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] hannonhill.com 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.

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.