====================================================================== SmartSockets CFIXes are cumulative and therefore this patch also includes the fixes addressed in CFIX 1 & 2. To see the complete release notes (including defects addressed in the previous CFIXes, or to download this patch please see the links below. ====================================================================== Reported fixes (TIB_ss_6.8.0_CFIX_V3)
* Fixed an issue that could sometimes cause clients to core if they traversed the `server_names' list many times, especially if using the PGM link driver. This was introduced in 6.8.0, and can be recognized by `could not connect to <server>' messages displaying corrupt names in place of <server>. (CR 1-7WSA9F)
* Changed RTserver to not allow clients with wildcards (i.e. `*' or `...') in their `unique_subject' to connect. Such clients could cause serious misbehavior because e.g. any message meant for a client with a `unique_subject' `/...' would be sent to the entire cloud. (CR 1-7X6HUG)
* Change Java/C# API's to throw an exception if a client at- tempts to set `ss.unique_subject' to a value containing a wildcard (i.e. `*' or `...'). Note that Java clients being recompiled must now catch this exception thrown from TipcOption.setValue if that method is being used. C# clients and previously compiled Java clients are unaffected. (CR 1-7X6HTV)
* Made a change to the Java API that should result in a significant performance improvement when sending messages with a very large number of fields. This fixes a problem that was introduced in 6.7.0. (CR 1-7XCOC3)
* Improved the topology change detection in CFIX 2 to catch a corner case that might happen in larger server clouds. (CR 1-1V6F8O)
Issue/Introduction
TIBCO SmartSockets 6.8.0 Hotfix 3 is now available