|
Release Notes
|
The most significant updates to UM version 6.15 are performance improvements for IPC and the persistent Store.
Also see Deprecations.
The following new features and enhancements apply to UMS, UMP, and UMQ products.
IPC Speedup. The code for the Transport LBT-IPC is better optimized, especially for multiple subscribers (fanout). No application or configuration changes are necessary to take advantage of this improvement.
SRS Monitoring. The SRS Service (TCP-based topic resolver) now publishes its operational statistics to the Monitoring Collector Service (MCS). See SRS Element "<monitor-format>". See Monitoring for an overview of monitoring an Ultra Messaging network.
Improved UDP Message Reception. When the multiple_receive_maximum_datagrams (context) option is used, memory management is now more efficient, leading to a small increase in maximum sustainable throughput.
MCS without license key. A UM license key is no longer needed to run the Monitoring Collector Service (MCS).
UDP Topic Resolution Reduction. Bug 11037 was fixed with an enhancement that provides a mild reduction in UDP-based topic resolution traffic when applications get an EOS event.
The following new features and enhancements apply to UMP and UMQ products.
Store Initialization Speedup. When a disk-based Store is restarted, it restores previously saved messages from the cache file. This message restoration is now optimized in two ways:
The following new features and enhancements apply to the UMQ product.
As of UM version 6.15, DRO enhancements/fixes are included in the streaming section and are applicable to UMS, UMP, and UMQ. This is because the DRO now included with all three products.
The following bug fixes apply to UMS, UMP, and UMQ products.
| Change Request | Description |
|---|---|
| 11063 | FIXED: A UM version 6.14 SRS can get into a state where control messages are sent and received at a very high rate. This is difficult to reproduce, and is related to a named Store being restarted on a network containing a DRO. SRS users with named Stores and DROs should upgrade at least their SRSes, DROs, and Stores to UM version 6.15. |
| 11055 | FIXED: An application can get a crash (seg fault) if an event queue is shut down while a context/XSP is still enqueuing events to it. |
| 11111, 11112, 11190 | FIXED: Application crash (seg fault) when configured for automonitoring using monitor_transport set to lbmsnmp. |
| 11146, 10387 | FIXED: When source-side filtering is enabled but there is a network problem leading to packet loss when the connection is being set up, the receiver can be deaf to messages. |
| 11269 | FIXED: When the DRO is configured to send stats using protobuf, the DRO portal-specific stats are not sent. |
| 11153 | FIXED: When a source send fails, typically due to an application coding or configuration error, UM improperly increments its internal sequence number state. |
| 11270 | FIXED: A small memory leak in the DRO when protobuf stats are enabled. |
| 11247 | FIXED: A wildcard receiver can leak a small amount of memory when a matching source exits and times out. |
| 11015 | FIXED: Store initialization very slow on large repository. This was fixed with a new feature: Limit Initial Restore with Restore-Last. |
| 11037 | FIXED: Spike in topic resolution seen after EOS is delivered to application. This was fixed with an enhancement that reduces topic resolution traffic after an EOS. No changes in code or configuration are needed to take advantage of this enhancement. |
| 10529 | FIXED: Added destination IP address to certain socket errors (including no route to host). |
The following bug fixes apply to UMP and UMQ products.
| Change Request | Description |
|---|---|
| 11206 | FIXED: Store can crash if configured for RPP, the Store is writing to disk, and the Store is restarted. |
| 11072 | FIXED: When a memory-only Store is run in RPP mode, a "down" blocking receiver will not block the source. Although this bug is fixed, Informatica does not recommend using a memory-only Store in RPP mode. |
| 11082 | FIXED: The Store can crash with a fatal assertion: |
| 11087 | FIXED: Persistent sources set with very large flight size limits (in the hundreds of thousands or more) can experience very long source registration times and shutdown times of many tens of seconds. The delays are now somewhat reduced, but very large flight sizes are not recommended. |
| 11127 | FIXED: If a Store is configured for sending daemon statistics over protobufs, the stats message can get too big to send. This is only when large numbers or sources and/or receivers are connected to the same Store process. Store monitoring messages are now separated into three messages. See Store Protobuf Monitoring for special upgrade instructions. |
| 11123 | FIXED: The Store can crash when the state/cache directory plus file name is more than 255 characters long. Note that even with the fix, the cache directory and the state directory paths are limited to 230 ASCII characters. If that limit is exceeded, UM will print an error and exit. |
| 11140 | FIXED: A publisher using the Smart Source API to send UM requests on a persistent source can fail with: |
| 11152, 11156 | FIXED: The Store can crash when sequence numbers roll over from 0xFFFFFFFF to 0, with the message: |
| 10166, 11162 | FIXED: If topic resolution and SRI messages don't arrive in proper order, a restarted store can be deaf to a source. |
| 9777 | FIXED: Store can crash with log message: |
| 11167 | FIXED: Store sometimes logs the warning: |
| 10552 | FIXED: When SRI requests time out in a persistent receiver due to a short-term network outage, the receiver can remain deaf after the network is restored. Retries were added. Note that warnings are logged periodically with each retry. |
| 11177 | FIXED: Proxy source can sometimes re-register on cleaned Store. |
| 10946, 10930 | FIXED: Proxy source can sometimes be repeatedly created and deleted by different stores ("rolling" behavior). |
| 11245 | FIXED: A misconfigured persistent publisher can result in a Store crash (seg fault). The specific configuration error is that the source's list of Stores has some Stores specified with registration IDs and others not. |
The following bug fixes apply to the UMQ product.
As of UM version 6.15, DRO enhancements/fixes are included in the streaming section and are applicable to UMS, UMP, and UMQ. This is because the DRO now included with all three products.
As of UM version 6.15, the "Reduced FD Store" feature is removed from the product. Users of reduced-FD should migrate to repository-type "disk".
For persistence users who enable proxy sources on their Stores, Informatica recommends enabling the new Store configuration option: Store Option "proxy-source-repo-quorum-required".
See Proxy Source Elections for details.
Due to bug 11127, the Store's daemon statistics using protobuf format had to be separated into three message types:
If you have written code to process protobuf format Store daemon stats, you will need to revisit that code. See Example ump_mon.proto for the Store's protocol buffer definition file. Your code can look at the message type to differentiate between old vs. new Store stats.
If you are upgrading from a UM version prior to 6.15, you must also examine the Special Upgrade Instructions for 6.14.