Release Notes

UM Version 6.7.3

The most significant update to UM version 6.7.3 is the repair of a critical bug that primarily affects the DRO when using peer links.

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

# Enhancements for 6.7.3 <-

## Streaming Enhancements for 6.7.3 <-

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

- Ultra Messaging 6.7.3 introduces the following new Java class and methods:
  - Class: com::latencybusters::lbm::LBMSerializedResponse
  - Method: com::latencybusters::lbm::LBMMessage::getSerializedResponse()
  - Method: com::latencybusters::lbm::LBMContext::respond()
  These methods allow Java applications to extract a serialized response (a byte array representation of the request originator's address) from a received request message, and allow either the same application or another application (if the byte array representation is passed to the other application, e.g., via a standard message) to use that serialized response to send a response to the request originator.

## Persistence Enhancements for 6.7.3 <-

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

- None.

## Queuing Enhancements for 6.7.3 <-

Note
  The brokered queuing and UM JMS functionalities were replaced in version 6.8, so most of these notes do not apply to more-recent versions of UM. However, ULB functionality is retained.

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

- None.

## Dynamic Router Enhancements for 6.7.3 <-

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

- None.

# Fixed Problems and Limitations for 6.7.3 <-

## Streaming Fixed Problems and Limitations for 6.7.3 <-

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

Change Request | Description
--- | ---
9508 | On Windows, an application might crash when a TCP receiver disconnects from a TCP source.
9515 | Multi-homed windows machines where the IP addresses of at least two NICs have the same number of digits might return the wrong IP address for an adapter name.
9516 | When using DRO peer portals, a peer disconnect might result in a deadlock, which causes the DRO to stop functioning and requires a restart.

## Persistence Fixed Problems and Limitations for 6.7.3 <-

The following bug fixes apply to UMP and UMQ products.

- None.

## Queuing Fixed Problems and Limitations for 6.7.3 <-

Note
  The brokered queuing and UM JMS functionalities were replaced in version 6.8, so most of these notes do not apply to more-recent versions of UM. However, ULB functionality is retained.

The following bug fixes apply to the UMQ product.

- None.

## Dynamic Router Fixed Problems and Limitations for 6.7.3 <-

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

- None.

# Special Upgrade Instructions for 6.7.3 <-

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

Also see Deprecations.