The most significant update to UM version 6.13.1 is an upgrade to the latest OpenSSL.

Attention: There are some special upgrade instructions for UM versions 6.13.1 and beyond that will affect some users upgrading from pre-6.13.1 versions of UM. See Special Upgrade Instructions for 6.13.1. For general upgrade instructions, see Upgrade Procedure. You are also advised to inspect the full list of Deprecations.

Enhancements for 6.13.1 <-

Streaming Enhancements for 6.13.1 <-

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

OpenSSL 1.1.1g. UM's Encrypted TCP feature has been upgraded to use OpenSSL version 1.1.1g.

Persistence Enhancements for 6.13.1 <-

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

None.

Queuing Enhancements for 6.13.1 <-

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

None.

Dynamic Router Enhancements for 6.13.1 <-

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

None.

Fixed Problems and Limitations for 6.13.1 <-

Streaming Fixed Problems and Limitations for 6.13.1 <-

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

Change Request

Description

10965

FIXED: UM on the Windows platform was not able to load XML configuration files via the HTTP protocol.

10932, 10970

FIXED: UM versions 6.12, 6.12.1, and 6.13 on Linux suffered a minor speed degradation, visible in certain minimal ping/pong tests. No degradation has been reported during testing of production applications.

As part of fixing this, the Linux 64-bit UM versions 6.13.1 and beyond must have access to a glibc of version 2.14 or higher. See Minimum Required Glibc Version.

10979, 10980

FIXED: Enabling Compressed TCP on the Solaris X86 64-bit platform can result in a segmentation fault inside "LZ4_copy8()".

Persistence Fixed Problems and Limitations for 6.13.1 <-

The following bug fixes apply to UMP and UMQ products.

10911, 10934

FIXED: The Store can fail with a segmentation fault or a fatal assert ("info->sqn == DMON_GET(repo, mem_trail_sqn)" when it is configured to use TCP-based Topic Resolution and it is restarted while the persistent source is actively sending.

10976, 10978

FIXED: If an SPP Store running UM version 6.12, 6.12.1, or 6.13 is restarted without deleting the state and cache files, it can enter a state where it does not resume persisting messages. That store also stops sending stability ACKs to the source.

Queuing Fixed Problems and Limitations for 6.13.1 <-

The following bug fixes apply to the UMQ product.

None.

Dynamic Router Fixed Problems and Limitations for 6.13.1 <-

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

None.

Special Upgrade Instructions for 6.13.1 <-

Minimum Required Glibc Version <-

Due to fixing bug 10932, some Linux users will need to use a newer version of the glibc library than is standard on their version of Linux. Linux 64-bit UM versions 6.13.1 and beyond must have access to a glibc of version 2.14 or higher. For example, RHEL-6 systems come standard with glibc 2.12. To determine the glibc shipped with a wide variety of Linux distros, see this distrowatch query for glibc (look for "Red Hat").

If your 64-bit Linux system does not have glibc 2.14 or higher, Informatica does NOT recommend replacing your existing glibc with a newer one.

The best approach is to upgrade to a newer version of Linux. Note that RHEL-6 will end its maintenance support on November 30, 2020.

However, we recognize that upgrading your Operating System is a disruptive and expensive activity. We have had good luck using glibc 2.14 on CentOS-6 (Red Hat's non-enterprise version of RHEL-6). Here are the steps we followed:

download glibc 2.14.
Build it locally. Do NOT install it in the standard location. You want the new version to co-exist with your OS's standard version.
To run an application with UM version 6.13.1 or beyond, set the environment variable "LD_PRELOAD" to the path of the "libc.so.6" file built in step 2.

Remember, you don't want to replace the standard glibc for your OS.

Finally, note that if your application was built against UM version 6.7 or beyond, you are not required to rebuild your application; you can simply use the existing executable. This glibc upgrade won't affect your application's use of glibc.

Previous Special Instructions <-

If you are upgrading from a UM version prior to 6.13.1, you must also examine the Special Upgrade Instructions for 6.13.