Release Notes
|
The most-significant update to UM version 6.11.1 is a set of performance improvements to the Persistent Store daemon. Some performance improvements were also applied to the data receive path for applications.
The following new features and enhancements apply to UMS, UMP, and UMQ products.
The following new features and enhancements apply to UMP and UMQ products.
The following new features and enhancements apply to the UMQ product.
The following new features and enhancements apply to the Dynamic Routing Option (DRO).
The following bug fixes apply to UMS, UMP, and UMQ products.
Change Request | Description |
---|---|
10385, 10280 | Enhancement: Reduced number of gettimeofday() calls in context loop. This lowers receive-side latency and CPU load. |
The following bug fixes apply to UMP and UMQ products.
Change Request | Description |
---|---|
10332, 10409 | FIXED: When the Persistent Store is configured to publish Daemon Statistics, there is a small chance that it will fail to initialize properly. It might log the error: |
10400, 10401 | FIXED: Bug in Persistent Store leads to performance degradation over time. (This bug has existed in the Store for many years.) |
10404, 10411 | FIXED: When using RPP with repository-type "disk", it is possible for a blocking receiver to get unrecoverable loss. This loss can be accompanied by the following warning in the Persistent Store log file: |
10406, 10407 | FIXED: A bug fix added to 6.10.1 accidentally introduced a significant performance reduction in the UMP Persistent Store. This regression is repaired in 6.11.1. |
The following bug fixes apply to the UMQ product.
The following bug fixes apply to the Dynamic Routing Option (DRO).
Starting with UM version 6.12, the UM daemons will no longer be available on certain platforms.
UM daemons will continue to be available on the following platforms:
The planned deprecated daemon platforms are:
User applications deployed on these platforms will fully interoperate with daemons running on the reduced set of platforms.
Please contact support if any of these planned deprecations interfere with your existing or planned deployments.