Apama 10.15.1 | Other Resolved Issues | Release 10.0.0 | Correlator
 
Correlator
*PAM-26964
It is no longer possible to inject the Management.mon file followed by the OutOfBandEventDefs.mon file, due to a change in the management plug-in which both use.
When injecting the Management.mon file followed by the OutOfBandEventDefs.mon file, the error message looked like:
Error injecting monitorscript from file
monitors/outofband/OutOfBandEventDefs.mon: Error on line 138: Trying
to return a 'sequence<unknown type>' from an action which returns
a sequence<com.apama.oob.ReceiverConnected> (error reported to
client)
This was fixed in 10.0.0.1. The OutOfBandEventDefs.mon file now uses the new OOBPlugin, not the ManagementPlugin, which removes an injection ordering dependency between Management.mon and OutOfBandEventDefs.mon.
*PAM-26730
Repeated calls to monitor.subscribe() cause memory leak.
In previous releases, calling monitor.subscribe() from EPL would allocate some additional memory for each call even if the current context was already subscribed, which in some cases would mean EPL applications would have needed to perform their own reference counting to avoid repeated calls using more memory. This has now been fixed and EPL applications can call monitor.subscribe() any number of times from a given context without any extra memory being allocated.
*PAM-27032
Correlator crashes with YAML configuration files with invalid spacing in maps.
The correlator would crash if a YAML file with invalid spacing in maps was provided. This has been fixed such that an error will be generated in lieu of crashing when invalid YAML files are read.
*PAM-27017
Changing storeLocation, storeName is broken when writing input log.
An error has been fixed in handling command line arguments where the correlator would always use the default persistence database name and location as the source to copy the persistence database into the input log.
*PAM-26826
Correlator crash when sending in malformed &TIME events.
This issue is with the correlator crashing on Windows while trying to parse an &TIME event containing a single backslash inside, for example:
&TIME("a")
The backslash was expected to be followed by a valid escape sequence such as n, quote, t etc. If the backslash was not followed by a valid escape sequence, then this resulted in an unhandled exception on Windows, causing a correlator crash.
This has now been fixed.