Release Notes
UM Version 6.12.1

The most-significant updates to UM version 6.12.1 are the introduction of .NET on Linux and a "busy wait" option for context threads.

Attention
There are some special upgrade instructions for UM versions 6.12 and beyond that will affect a small percentage of users upgrading from pre-6.12 versions of UM. See Special Upgrade Instructions for 6.12.


Enhancements for 6.12.1  <-


Streaming Enhancements for 6.12.1  <-

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

  • UM now supports the Microsoft .NET framework on 64-bit Linux. See Using UM .NET on Linux.

  • The Network Socket Busy Waiting feature can be used to prevent a context or XSP thread from sleeping while waiting for network events, such as received packets. This can reduce latency and especially latency outliers (jitter).

  • The dependency between UM and the OpenSSL libraries is now optional. If the libraries are not used, then they do not need to be present on the system. See OpenSSL Dependency for more information.


Persistence Enhancements for 6.12.1  <-

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

  • None.


Queuing Enhancements for 6.12.1  <-

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

  • None.


Dynamic Router Enhancements for 6.12.1  <-

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

  • None.


Fixed Limitations for 6.12.1  <-


Streaming Fixed Limitations for 6.12.1  <-

The following bug fixes apply to UMS, UMP, and UMQ products.

Change Request

Description

10702, 10713, 10741

FIXED: UM has a load-time dependency on a specific version of OpenSSL. If the expected version is not present, the application can be unable to load and run, or it can write warning messages to the log file (Core-9565-109 and Core-9728-14), even if encryption services are not configured for use.

For more information, see OpenSSL Dependency.

10792, 10793

FIXED: When an application is built with the UM 6.12 static library, diagnostic error information might not be properly communicated from a failed API call. A bad status will be returned, but the error code and message will be empty. To our knowledge, there will be no adverse behavior, but the loss of error information makes problem diagnosis very difficult.

This problem is fixed in UM version 6.12.1 and beyond.

none

FIXED: The UM documentation main page does not render correctly in some environments, possibly due to the use of deprecated HTML frames.

The UM documentation main page is now simplified.


Persistence Fixed Limitations for 6.12.1  <-

The following bug fixes apply to UMP and UMQ products.

Change Request

Description

9940, 10131, 10651, 10734

FIXED: If a persistent publisher sends a message containing one or more Message Properties, and the Proactive Retransmission feature is used to record the message on the Store, a receiver which recovers the message from the Store will crash with a fatal assert:
FATAL: failed assertion [prop_offset >= 0]

10676, 10735

FIXED: Loss of packets into Store Daemon blocks stability ACKs. This increases the likelihood of a source blocking on flight size.

10765, 10788

FIXED: Store log always contains "[WARNING]: Core-5688-28: context config variable receive_thread_pool_size is deprecated. Has no effect."


Queuing Fixed Limitations for 6.12.1  <-

The following bug fixes apply to the UMQ product.

  • None.


Dynamic Router Fixed Limitations for 6.12.1  <-

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

  • None.