|
Release Notes
|
The most significant update to UM version 6.14 is further enhancement of TCP-based Topic Resolution (DRO compatibility).
Also note UM version 6.14 announces the deprecation of several features. See Deprecations.
The following new features and enhancements apply to UMS, UMP, and UMQ products.
SRS and DRO. TCP-based Topic Resolution now has full functionality (except lbmrd-based Network Address Translation (NAT), which is not planned at this time). Users of DRO can now use the SRS instead of UDP-based TR. See TCP-Based Topic Resolution Details. Includes the introduction of a new configuration option: resolver_disable_udp_topic_resolution (context).
Monitoring. A new monitoring infrastructure is available which unifies transport statistics with Store and DRO statistics. As part of this, automatic monitoring now supports reporting of topic-to-transport mappings. See Monitoring and Monitoring Collector Service (MCS).
Fragmentation and MTU. Dynamic Fragmentation Reduction allows users of kernel bypass drivers (like Solarflare's Onload) to avoid premature UM fragmentation of messages into multiple datagrams that should fit in a single MTU, while also avoiding IP fragmentation that can happen if datagram max size is set above 1472. See Dynamic Fragmentation Reduction.
Note: this enhancement should address known issue 10985.
The .NET API now supports XSP. See Example lbmrcvxsp.cs.
Smart Source Requests. The Smart Source C API now supports the sending of UM requests. Note that this enhancement does not support Java, .NET, UM fragmentation, message properties, or spectrum channels. See Request/Response, lbm_ssrc_send_request_ex() and Example lbmssrcreq.c.
Sparc, Darwin (MacOS / OSX). Informatica no longer ships the Sparc or Darwin (MacOS / OSX) platforms with every new version of UM. Instead, Sparc and Darwin are now considered "on demand" platforms. Note that Sparc and MacOS are still supported platforms for UM. Customers of the Sparc and/or Darwin platforms may specifically request that a build be generated for the most-recent general UM version.
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 |
|---|---|
| 10863 | FIXED: A variety of UM configuration validation error messages do not report the topic name associated with the invalid configuration. |
| 10965 | FIXED: Starting with UM version 6.11, Windows UM cannot load XML configuration files via HTTP. |
| 10997 | FIXED: The SRS is missing the "-E" command-line option for setting environment variables for Windows services. |
| 10992 | FIXED: The various UM example applications are inconsistent regarding the treatment of multiple "-c file1 -c file2" options on a command line. Some apps will load every file specified, but some apps will only load the last file specified. All application now support multiple "-c file1 -c file2" options in the same way: by loading every file specified. |
| 10654 | FIXED: When UM detects outages of unicast Topic Resolution, the logs were classified as "notice" or "warning". However, since the loss of topic resolution can lead to "deafness", the messages should be classified as errors. This is especially a problem for the DRO. This change applies to all applications and daemons. Note that the message was given a new ID number.
This change applies only to the DRO:
Finally, note that for non-DRO components, including user applications, the following message remains as a notice:
|
The following bug fixes apply to UMP and UMQ products.
| Change Request | Description |
|---|---|
| 11019, 11053 | FIXED: A change in UM version 6.13 resulted in SPP-configured persistent sources experiencing periodic latency outliers and hitting flight size (LBM_EWOULDBLOCK send failures). |
| 11046 | FIXED: The persistent Store process can hang during initialization on Windows-64. This has only been seen on 64-core servers. A stack trace indicates the hang is inside the SmartHeap 3rd party package. |
| 11046 | FIXED: The persistent Store process can hang during initialization on Windows-64. This has only been seen on 64-core servers. A stack trace indicates the hang is inside the SmartHeap 3rd party package. |
| 11026 | FIXED: The persistent Store process can experience severe memory growth over time. This has only been seen on Windows-based 64-bit servers. The problem has been traced to the SmartHeap 3rd party package. |
| 11022 | FIXED: The umesnaprepo example application cannot be built on Windows due to unresolved symbols lbm_srp_... |
| 11005 | FIXED: If an SPP store experiences unrecoverable burst loss, it can lead to significant memory growth. |
| 8013, 11000, 11001 | FIXED: If an RPP Store had to write some messages to disk at some point in the past, and then the Store and publisher restart, the source can restart at the wrong sequence number. |
| 10984 | FIXED: If a persistent receiver is assigned to an XSP, a memory corruption can happen resulting in unpredictable behavior, including crashes. |
| 10981 | FIXED: If a non-UME example application is configured to use persistence, the unexpected events delivered did not produce helpful error messages. |
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.14, users should compile C programs with an additional include directory. Prior to UM 6.14, applications only needed to supply "-I $UM_PLAT/include" where "$UM_PLAT" is the path to the platform-specific directory of a UM installation. In versions 6.14 and beyond, applications should supply "-I $UM_PLAT/include -I $UM_PLAT/include/lbm".
For example:
gcc -I /UMP_6.14/Linux-glibc-2.17-x86_64/include \
-I /UMP_6.14/Linux-glibc-2.17-x86_64/include/lbm \
...
Without this, you may encounter a build error where the compiler is unable to find the include file "gen/um_mon_attributes.pb-c.h".
If you are upgrading from a UM version prior to 6.14, you must also examine the Special Upgrade Instructions for 6.13.1.