Release Notes
UM Version 6.11.1

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.

Attention
See Deprecations for 6.11.1 for important information regarding future platform support for UM daemons.


Enhancements for 6.11.1  <-


Streaming Enhancements for 6.11.1  <-

The following new features and enhancements apply to UMS, UMP, and UMQ products.

  • Performance improvements made to the data reception code paths, including reduction in calls to gettimeofday(), and some localized code optimizations.


Persistence Enhancements for 6.11.1  <-

The following new features and enhancements apply to UMP and UMQ products.


Queuing Enhancements for 6.11.1  <-

The following new features and enhancements apply to the UMQ product.

  • None.


Dynamic Router Enhancements for 6.11.1  <-

The following new features and enhancements apply to the Dynamic Routing Option (DRO).

  • None.


Fixed Limitations for 6.11.1  <-


Streaming Fixed Limitations for 6.11.1  <-

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.


Persistence Fixed Limitations for 6.11.1  <-

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:
[CRITICAL]: Store-10184-80: umestore_dmon_publish: CoreApi-5688-2996: src must be valid
and could exit with a segmentation fault.

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:
[WARNING]: WARNING: failed assertion [ntohl(ohdr->sqn)==rec->sqn]

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.


Queuing Fixed Limitations for 6.11.1  <-

The following bug fixes apply to the UMQ product.

  • None.


Dynamic Router Fixed Limitations for 6.11.1  <-

The following bug fixes apply to the Dynamic Routing Option (DRO).

  • None.


Deprecations for 6.11.1  <-

Attention
This section of the 6.11.1 release notes announced the deprecation of certain platforms for UM daemons, claiming that they would be discontinued in UM version 6.12. However, some users requested more time for the transition. As of UM version 6.12, these deprecated daemon platforms have not yet been removed, and are therefore still fully supported in 6.12 (contrary to what is written below). See Platform Deprecations for Daemons.

Starting with UM version 6.12, the UM daemons will no longer be available on certain platforms.

Note
User applications will continue to be fully supported on all platforms. These deprecations only apply to UM daemon executables, such as the Store Daemon and the Dynamic Router daemon.

UM daemons will continue to be available on the following platforms:

  • Persistent Store daemon ("stored"): Linux 64-bit, Windows 64-bit.
  • UM Dynamic Router daemon ("tnwgd"): Linux 64-bit, Windows 64 and 32-bit.
  • UM Manager daemon ("ummd"): Linux 64-bit, Windows 64-bit.
  • UM Resolution daemon ("lbmrd"): Linux 64-bit, Windows 64-bit.
  • UM Queue Broker (ActiveMQ): Linux 64-bit, Windows 64-bit.

The planned deprecated daemon platforms are:

  • Solaris (X86 and Sparc)
  • AIX
  • MacOS
  • Linux 32-bit
  • Windows 32-bit (except Dynamic Router "tnwgd", which will continue on 32-bit)

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.