Release Notes

UM Version 6.16.1

The most significant updates to UM version 6.16.1 are the "NAK Cutoff" feature and Persistence bug fixes.

Attention
  There are some special upgrade instructions for UM versions 6.16 and beyond that will affect some users upgrading from pre-6.16 versions of UM. See Special Upgrade Instructions for 6.16. For general upgrade instructions, see Upgrade Procedure.

# Enhancements for 6.16.1 <-

## Streaming Enhancements for 6.16.1 <-

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

- NAK Cutoff. The "NAK cutoff" feature allows an application to force its context(s) to stop sending NAKs (LBT-RM only), even if packet loss is detected. See NAK Cutoff.

## Persistence Enhancements for 6.16.1 <-

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

- None.

## Queuing Enhancements for 6.16.1 <-

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

- None.

# Fixed Problems and Limitations for 6.16.1 <-

## Streaming Fixed Problems and Limitations for 6.16.1 <-

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

Change Request | Description
--- | ---
11468, 11457, 11396 | FIXED: When UM is configured for TCP-based topic resolution with the SRS, the monitoring data does not include SRS connection event statistics.
11467, 11433 | FIXED: A publisher can get the warning assert `"[new_duration!=0]"` when resolver_query_minimum_sustain_duration is 0.

## Persistence Fixed Problems and Limitations for 6.16.1 <-

The following bug fixes apply to UMP and UMQ products.

11483, 11439, 11338 | FIXED: A persistent receiver that experiences unrecoverable loss before the first successfully-received message will not deliver an unrecoverable loss event.
11466, 11444 | FIXED: When a persistent and a non-persistent source are created for the same topic, the Store will send SRI requests to the non-persistent source, resulting in perpetual log messages for the non-persistent source.
11465, 11437 | FIXED: A persistent publisher can get the fatal assert "[rctxinfo->rctx==NULL]" during the deletion of a context if final advertisements are configured.

## Queuing Fixed Problems and Limitations for 6.16.1 <-

The following bug fixes apply to the UMQ product.

- None.

# Special Upgrade Instructions for 6.16.1 <-

There are no upgrade instructions specific to 6.16.1. However, if you are upgrading from a version prior to 6.16, then you must examine the Special Upgrade Instructions for 6.16.

Also see Deprecations.