Correlator persistence can now only be enabled with a valid license file. Otherwise, it will not be possible to run the correlator in persistent mode.

Apama supports various licensing models, one of which is licensing per physical CPU core. In previous releases, any restrictions on the number of licensed cores were not enforced. In this release, the number of threads that can be used for running Apama applications will be capped at the number of cores specified in the license, if the correlator is run on a machine that has more cores than the license allows. The correlator will log a WARN message to make it clear when this has happened. If you have previously been running with an insufficient license, then you may experience a corresponding reduction in performance after upgrading.

The Ant macro <start-correlator> (generated by the Ant Export feature) checks whether there is already a correlator running. However, previously that was ignored allowing <start-correlator> to succeed even if a new correlator with the specified parameters was not started. Now it will log a warning and (by default) fail the task if a correlator is already running. An Ant build script exported from a launch configuration with Reuse Correlator selected will therefore now fail. To return to the previous behavior, edit the build.xml to set the failoncorrelatorrunning=false attribute on the <start-correlator> task, or set the global property correlator.failonrunning, for example, by specifying -Dcorrelator.failonrunning=false on the command line when executing Ant.

When you upgrade to a new major version of the product, you must regenerate any CDP that was created by exporting query files or scenario definitions from the previous version.