|
UMDS Release Notes
|
The most-significant update to UMDS version 6.14 is the introduction of compression for the client/server connection.
UMDS version 6.14 should be run on UM version 6.14 or beyond.
The following new features and enhancements apply to the UMDS product.
Compression. The TCP connection between the UMDS server and client can now be compressed to reduce the bandwidth requirement. See Client Compression.
Log file rolling. The UMDS server now supports the automatic splitting of its log file into separate files based on time and/or file size ("rolling"). See Log Handling.
Total Queue Size Limit. In earlier versions, users wanting to use Per-Topic Message Queues with large numbers of topics risked very large memory consumption by the UMDS Server. Starting with UMDS version 6.14, a total queue size limit can be configured. See the UMDS Element "<server>" attribute "total-q-size-limit".
The following bug fixes apply to the UMDS product.
| Change Request | Description |
|---|---|
| 11414 | FIXED: Illegal memory access by UMDS Server with Late Join enabled. |
| 11406 | FIXED: UMDS Server crash with segmentation fault when monitoring is enabled and large numbers of topics are subscribed and published. |
| 11401 | FIXED: UMDS Server can experience unbound memory growth in Per-Topic Message Queues if the incoming message rate consistently exceeds the client's ability to keep up. |
| 11265, 11363 | FIXED: The UMDS .NET client library can take multiple seconds to connect to a server due to a DNS timeout even though the servers is specified with numeric IP addresses. |
| 11361 | FIXED: The Windows installer for UMDS adds an empty directory to the PATH variable. |
| 11355, 10886 | FIXED: When the UMDS server is restarted, it deletes the contents of the previous log file. This risks losing valuable diagnostic information. "Append" is preferred. Starting with UMDS version 6.14, the server will open its log file with "append" behavior after a restart. See Unbounded Log File Growth and Log Handling. |
| 11324, 10003 | FIXED: Certain coding errors in client applications can cause the UMDS server to crash with a segmentation fault. While the root cause is user error, we made the UMDS Server more robust in the face of client coding errors. |
| 11054 | FIXED: If Using UMDS Client Encryption is being used and a large message is sent, the server can log "lbm_openssl_socket_write: sock fd 41 SSL_write failed" and disconnect the client. |
When a pre-6.14 version of the UMDS server restarts, it clears an existing log file and starts it from zero.
Due to fixing bug 10886 in UMDS version 6.14, restarting the server will re-open an existing log file in "append" mode and write new logs to the end of the file. Thus, over time, the log file grows without bound.
Users wishing to retain the older "start from zero" behavior will need to rename or delete the log file themselves immediately before starting the server.
Alternatively, UMDS 6.14 now supports automatic log file rolling based on time and/or file size.
See Log Handling.
The UMDS server's XML configuration file version has increased to version 1.1.
It is not required that existing version 1.0 configuration files be modified. Only if you desire the new functionality available in UMDS version 6.14 do you need to increase the version number to 1.1.
For example:
<?xml version="1.0" encoding="UTF-8"?> <umds-daemon version="1.1"> ...
Note that it is not the XML version that changed, it is the umds-daemon version.