Apama 10.15.4 | Readme | Resolved Issues | Release 10.7.1
 
Release 10.7.1
Correlator
*PAM-32297
Correlator crashes when libnss_ldap is configured on system for SSL.
There is a known issue with running Apama on systems configured to use libnss_ldap in-process. This applies to any system authentication method using SSLwhich does not use an external daemon. This is due to the custom OpenSSL shipped with Apama. The work around is either to disable SSL for your LDAP requests or, preferably, configure the system with an external authentication provider such as SSSD or nslcd, rather than libnss_ldap directly.
*PAM-31918
Sending in large (8Mb) managed object uses disproportionately large amounts of memory ( > 1Gb).
The ordering of entries in containers within EPL and within connectivity plug-ins is undefined in some cases. A change in this release to reduce memory usage had the side effect of changing some of this ordering. This is particularly likely to be reflected in the order of entries in maps when printed by some connectivity plug-ins like the diagnostic codec or the JSON format produced by the JSON plug-in. It could also affect the order that map entries are iterated over in your own plug-ins.
*PAM-32155
EPL on completed InnerEvent() crashes the correlator.
A correlator crash has been fixed. The crash occurred when a monitor was deleted which contained both an event type defined within its scope (an “internal event”) and an on completed listener for such events.
*PAM-32070
Correlator should allow starting during grace period after license expiry.
The correlator now starts with an expired license in its grace period, that is, 7 days post expiration date.
*PAM-32036
Incorrect type for runtime object of any.getGenericAction().
Calling getGenericAction on an any value that is an action, a value of type action<sequence<any> > returns any is returned. However, after assigning the return to an any, a call to getTypeName() would return the original action's type which would match the original signature, not action<sequence<any> > returns any, for example, would be a type mismatch. The correct type is now returned by getTypeName().
*PAM-32000
GenericComponentManagementAdapter::getHostname deallocates its return value.
An issue leading to corrupted data in the Prometheus hostname metric has been fixed.
*PAM-31960
Combination of big events and channel prefixes can cause a crash in engine_send, correlator (EventStreamReader).
Parsing an event (.evt) file with single lines in excess of 256kB combined with lines using a channel name before the event could result in a crash. This issue is resolved.
*PAM-31887
Correlator crash handler should log EPL monitor name etc. if possible.
In case of a correlator crash, after the correlator stacktrace, the EPL stacktrace is now printed as well.
*PAM-31932
New soft-reserved keywords have been added to the Event Processing Language (EPL). The await keyword is now a soft-reserved keyword.
This may become a language feature in the future, so it is recommended to avoid using it to avoid confusion.
Management Tools
*PAM-31996
httpserver_passman silently fails if httpasswd is not writeable.
httpserver_passman used to silently ignore if the httpasswd is not writable. Now it throws an error, stating a permission issue.
Cumulocity IoT Transport
*PAM-32088
senderAddress and senderName are required fields for sending SMS messages to Cumulocity IoT.
When the HTTP client generic JSON bundle is added to the project configuration, defaults for the sender name and sender address are now retrieved from the tenant options in Cumulocity IoT if they are not specified in the SendSMS event. If the tenant options cannot be retrieved from Cumulocity IoT, you can now configure the defaults by adding CUMULOCITY_SMS_SENDER_NAME and CUMULOCITY_SMS_SENDER_ADDRESS to the .properties configuration file of the Cumulocity IoT transport.
*PAM-31998
Cumulocity IoT ObjectCommitted/ObjectCommitFailed responses are sent on the default channel.
It is now possible to receive responses for the creation or update of predefined types (Measurement, ManagedObject, Alarm, Event, MeasurementFragment, and Operation) on their respective SUBSCRIBE_CHANNEL.
*PAM-31593
Generic requests should correctly support DELETE request where the body is empty.
On a Cumulocity IoT GenericRequest, a GenericResponseComplete acknowledgement is now sent even when the content-type is not set.
EPL Plug-ins
*PAM-32139
HTTP client: Query value incorrectly converted to ISO-8859-1.
The HTTP client and HTTP server connectivity transport plug-ins are no longer converting UTF-8 characters to ISO8859-1 for query string and path.
Dashboards
*PAM-31260
APAMA_DASHBOARD_CLASSPATH is not honored from environment when launching from Software AG Designer.
The APAMA_DASHBOARD_CLASSPATH environment variable can now be used when launching dashboards from Software AG Designer, thereby matching the behavior when opening dashboards from the command line.
Software AG Designer
*PAM-31672
NPE while adding JNDI environment property using JMS Configuration Wizard.
An error could occur when attempting to add a connection property to a Universal Messaging Correlator JMS Adapter as part of the configuration wizard. This issue has been resolved.
*PAM-31092
Data player not removing ADBCStatusManager.mon when launching project with xclock and timestamps from data.
The data player reliably removes ADBCStatusManager.mon now if it is externally clocked.
Connectivity and Adapters
*PAM-32221
Mapper codec fails to find item in map.
Incorrect comparison of map_t::iterators in C++ connectivity plug-ins is now detected. If it occurs, an exception “Invalid comparison of iterators into different maps” will be thrown. The correct course of action is to identify the source of the bug and fix it. For operational purposes, the exception may be suppressed by the existence of the environment variable AP_SKIP_DATA_T_ITERATOR_CHECKS.
*PAM-31928
JMS BEST_EFFORT queue receiving with IBM MQ is painfully slow.
For customers using JMS to receive non-persistent messages from an IBM MQ queue, a change was made (the default receiver maxBatchSize is now 1, that is, AUTO_ACK not CLIENT_ACK) which can enable significant performance improvements if you also add the ?READAHEADALLOWED=YES MQ property to the queue URL (see the IBM documentation for further information about the read-ahead allowed option). This change does not affect other JMS vendors, does not affect topics, and does not affect persistent (reliable) messages.