UMDS Release Notes
UMDS Version 6.0

UMDS version 6.0 includes all functionality and fixed limitations of version 6.0.200. Version 6.0 should be considered the next version after 6.0.200. Think of the ".200" version number as being like a negative number; 6.0.200 is less than 6.0.

The most-significant update to UMDS version 6.0 is the availability of Late Join for UMDS receive and sending client applications.


Enhancements for UMDS 6.0  <-

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

  • You can now use Ultra Messaging Late Join with UMDS Client receive applications, as well as with UMDS Client send applications.
  • The UMDS Web Monitor user interface now includes more detailed displays with help tooltips, server and connection control buttons, and a configuration file display. The Web Monitor also displays more detailed message statistics, with messages broken out by type and number of bytes sent and received. The new Web Monitor has improved design and readability.
  • The UMDS 6.0 Server is backward compatible with UMDS 1.1.1 clients.
  • The UMDS Server console log now includes the IP addresses and port numbers of client connections.
  • The example applications now monitor the number of source and receiver close acknowledgements. The example applications also monitor the number of requests that have timed out at the server. These applications log to the console, as appropriate, the number of requests sent and request cancellations received, the source and receiver closes sent, and close ACKs received. The example applications do not wait indefinitely, but continue after an arbitrary time. You can adjust the time limits in these examples as needed.
  • You cannot use, and are no longer required to use, permissions options. UMDS now ignores all permission configuration settings.
  • You can now use the Windows UMDS Client installer, UMDS_6.0_client-install.exe, for either 32-bit or 64-bit Windows.


Fixed Limitations for UMDS 6.0  <-

The following bug fixes apply to the UMDS product.

Change Request

Description

7499

FIXED: A UMDS Client cannot close a source or receiver while being disconnected from the server.

As a solution, sources and receivers can now call close() while disconnected from the server. When the client reconnects and re-established the closed element, the client library automatically issues the source or receiver delete command, completing the close process.

8168

FIXED: The server might crash after taking too long to service requests to refresh a Web Monitor display, or to create or delete a client connection.

8218

FIXED: Authentication by application name fails.

8418

FIXED: You cannot specify the size of a request independently of the message size in the umdsrequest sample application.

8482

FIXED: The UMDS Server log inserts an empty line after each log message.

8500

FIXED: When a UMDS send fails and does not return an EWOULDBLOCK, the UMDS Server does not log an error message.

8524

FIXED: Wildcard Receiver throughput performance degrades with high numbers of topic matches.

8530

FIXED: The UMDS Server does not set the retransmission flag for OTR recovered messages before forwarding those messages to a UMDS Client.

8542, 8547

FIXED: With transport LBT-SMX you cannot receive messages or send requests.

As a solution, you now cannot configure transport LBT-SMX with UMDS.

8545

FIXED: If you enable multithreaded transports, the UMDS Server encounters multiple error conditions.

As a solution, you can no longer enable multithreaded transports within the UMDS Server.

8561, 8822

FIXED: UMDS Client applications might crash due to a situation where the application cannot create a debug log file, but then tries to write log entries to the nonexistent debug log file.

8619

FIXED: The UMDS Server cannot send error messages reported by a UMDS client before that UMDS Client starts to send.

As a solution, the following new states track which commands the UMDS Client has sent to the UMDS Server and which commands the UMDS Server has responded to.

  • SOURCE_CREATE
  • RECEIVER_CREATE
  • SOURCE_DELETE
  • RECEIVER_DELETE
  • CONNECT
  • LOGIN_COMPLETE
  • LOGOUT_COMPLETE

8656

FIXED: The UMDS Web Monitor truncates longer topic names.

8697

FIXED: If you configure more workers than the host machine can support, the UMDS Server crashes with the following message:

[emergency] FATAL: failed assertion [err==0] at line 1645 in
../../../../../src/umds/umdsd/umdsd_worker.c

As a solution, if you configure too many workers, you see a warning message.

8700

FIXED: The UMDS Server needlessly issues the following warning:

Core-5688-1793: WARNING: Requested receiver attributes will be ignored,
previous receiver for topic [s] has already defined the attributes.

8753, 8754

FIXED: The UMDS Server might crash when receiving malformed packets.

8777

FIXED: The UMDS Server might crash when UMDS Client applications send at a high rate.

8786

FIXED: UMDS Clients might unexpectedly disconnect and reconnect due to a race condition.

8912

FIXED: The UMDS Server might crash when an enabled Web Monitor receives requests for details about an invalid connection.

8930

FIXED: The Java UMDS Client closes System.err when creating a debug log file.

8951

FIXED: If a message queue size limit is set to 0, the UMDS Server fails to discard messages older than the configured message age limit.

8985

FIXED: Example application server authentication fails if you connect and supply a username and password without an application name.

As a solution, you can now use command line option -A with the example applications to suppress sending their application name.

8986

FIXED: The UMDS Client .NET example umdssend application reports statistics with erratic timing intervals.

9006

FIXED: The UMDS Server might crash under conditions of heavy loss when a receiver client disconnects.

9057

FIXED: When a UMDS Server disconnects from a Java or .NET UMDS Client, the client issues a NULL pointer exception.

9058 FIXED: While a UMDS Client connection is closing, you might see the following warning message:
WARNING :Invalid state CLOSING for message 71