![]() ![]() įIXED: 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. : FATAL: failed assertion įIXED: If topic resolution and SRI messages don't arrive in proper order, a restarted store can be deaf to a source.įATAL: failed assertion. If that limit is exceeded, UM will print an error and exit.įIXED: A publisher using the Smart Source API to send UM requests on a persistent source can fail with:įATAL: failed assertion įIXED: The Store can crash when sequence numbers roll over from 0xFFFFFFFF to 0, with the message: Note that even with the fix, the cache directory and the state directory paths are limited to 230 ASCII characters. See Store Protobuf Monitoring for special upgrade instructions.įIXED: The Store can crash when the state/cache directory plus file name is more than 255 characters long. Store monitoring messages are now separated into three messages. This is only when large numbers or sources and/or receivers are connected to the same Store process. ![]() ![]() The delays are now somewhat reduced, but very large flight sizes are not recommended.įIXED: If a Store is configured for sending daemon statistics over protobufs, the stats message can get too big to send. This is VERY difficult to reproduce.įIXED: 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. When the Store experiences unrecoverable loss during late join, incoming data, and data being written to disk. Persistence Enhancements for 6.15 sqn = DMON_GET(repo, mem_trail_sqn)] Bug 11037 was fixed with an enhancement that provides a mild reduction in UDP-based topic resolution traffic when applications get an EOS event. A UM license key is no longer needed to run the Monitoring Collector Service (MCS). 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. See Monitoring for an overview of monitoring an Ultra Messaging network. This causes a problem for recent Linux distributions that no longer contain that library.įIXED: The DRO can abort with a fatal assert, "[buff->len". Introduction =LBM_SRC_TSNI_LENGTH]", if the transport datagram maximum size is set to 500 (the documented minimum).įIXED: The Linux UM library "liblbm.so" had an unnecessary dependency on libnsl.so. Ultra Messaging (Version 6.16) Release Notes ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |