Apama 10.15.1 | Other Resolved Issues | Release 10.5.0 | Correlator
 
Correlator
*PAM-30828
Performance issue in any type - calling loadAllConstants too much (fixed in 10.5.0.1).
Performance has been improved in EPL reflection using any objects, particularly the hasAction and getAction calls.
*PAM-30880
Engine connect YAML flips meaning of mode=legacy/parallel (fixed in 10.5.0.1).
An issue has been fixed where specifying the correlator connect mode in the YAML file interpreted legacy as parallel and vice versa.
*PAM-30594
Overwriting a valid license file with another valid license file can sometimes kill the correlator (rare race).
When updating the Apama license file for the correlator it was possible to exit due to an invalid license file, even when the file was valid. This issue has been fixed.
*PAM-30565
Prometheus metrics printed with locale-specific number formatting with Java enabled.
In some locales, it was possible for the Prometheus integration to return invalid numeric data. This issue has been resolved.
*PAM-30025
Re-reading and updating license files does not work correctly.
It was possible to replace the Apama license file and the correlator failed to update to the new license details. This has now been fixed.
*PAM-30018
Platform::generateUniqueId() is not unique in Docker containers with --network host.When running multiple “engine_” tools from Docker containers with --network host started at the same time, the tools could get disconnected. This has been fixed by adding additional checks for generating unique physical IDs on Linux.
*PAM-30017
dictionary.remove never decreases the size of the dictionary object.
EPL dictionary objects which were very large and then shrunk via the dictionary.remove method could still use a lot of memory. The dictionary.remove method has been changed so that it can shrink the underlying data structure when it is much larger than now necessary.