Apama 10.15.4 | Readme | Resolved Issues | Release 10.11.3
 
Release 10.11.3
Connectivity and Adapters
*PAM-33337
Kafka Java client plug-in throws LoginException: unable to find LoginModule class.
The Kafka Java client plug-in LoginException "unable to find LoginModule class" has been fixed. It now successfully constructs consumers and producers when sasl.jaas.config is provided in the connectivity.yaml configuration file.
Correlator
*PAM- 33416
Correlator status line generation is expensive when the number of chains or user status items is large.
The correlator log line generation used to be expensive when a lot of user status was created. Now the log line generation no longer depends on the number of user status items created.
Cumulocity IoT Transport
*PAM-33039
Upgrade Cumulocity IoT SDK to pick up Cumulocity IoT fix for vulnerable third-party component spring-web (found in Docker image).
The Cumulocity IoT client SDK has been updated to the latest version 1011.0.16 which removes CVE-2021-22118.
*PAM-33372
Cumulocity_Rest_API.mon populates incorrect tenantId in TenantDetails for per-tenant use cases.
When deployed in a per-tenant environment, the tenantId in the ApplicationSubscribedForTenant notification was incorrectly populated with the tenantId of the bootstrap tenant instead of the current tenant. This issue has been resolved.
*PAM-33411
Cumulocity_Rest_API.mon is not scalable with a large number of tenants.
When deployed in a multi-tenant environment, Cumulocity_Rest_API.mon used to take O(n^2) space. This issue has been resolved. It now takes a linear amount of space with respect to the number of tenants.
Software AG Designer
*PAM- 33441
"Open declaration" and "Open definition" sometimes do not open at the correct file/location.
"Open Declaration" was incorrectly calculating the matching file for the action members when there were multiple files in the same package declaration. This has now been fixed and the right file and action definition are shown upon selecting the "Open Declaration" in the EPL editor for the action members.
Other
*PAM-32882
Upgrade jdom.jar to avoid security advisories.
The JDOM v1 library has been removed from the Apama classpath to resolve security vulnerability CVE-2021-33813. In the unlikely event you have custom Java classes which were making use of the (undocumented/unsupported) presence of the JDOM v1 API on the classpath (org.jdom.*), you will need to add your own copy of JDOM v1 to the classpath or change your classes to use a different library such as JDOM v2+.