.. include:: ../vars.rst .. _section-whats-fixed-612: What's Fixed in 6.1.2 ===================== Type Containing Typedefs Caused INFO-Level Log Message about Different Type Definitions --------------------------------------------------------------------------------------- If a type containing a typedef was provided to |RS| through XML, the following INFO-level log message was printed when an endpoint using that type was discovered: .. code-block:: console ROUTERDdsDiscovery_assertType:found two different type definitions with the same name= This happened because, internally, |RS| did not maintain information about the typedef in the type. This did not cause any problems related to discovery mismatches or communication failures. This issue has been resolved. |RS| now uses the full type-definition, including typedefs, to compare with types found discovery. [RTI Issue ID ROUTING-971] Fourth Digit of Product Version not Logged at Startup ----------------------------------------------------- |RS| did not log the fourth digit (revision) of the product version at startup. This issue has been resolved. [RTI Issue ID ROUTING-975] Stream-Query Propagation did not Work when Using More than One Session ---------------------------------------------------------------------- When propagating stream-query result samples, |RS| may have sent corrupted data if the configuration used more than one session and both sessions were writing stream-query samples at the same time. This issue has been resolved. [RTI Issue ID ROUTING-997] Samples Published Out of Order from Same Virtual GUID were Dropped ------------------------------------------------------------------ If |RS| received samples for a given virtual GUID with sequence numbers that were out of order, |RS| dropped samples with sequence numbers lower than the highest received sequence number. This issue has been resolved. [RTI Issue ID ROUTING-928] Routing Service Crashed if -maxObjectsPerThread Set Too Small -------------------------------------------------------------- |RS| crashed if the command-line option ``-maxObjectsPerThread`` had a value less than 1024. This issue, which also affected |RECS|, has been resolved. Now instead of crashing, the service will log a warning and the default value will be used: .. code-block:: console Max objects per thread can't be lower than 1024. Setting MaxObjectsPerThread to 1024. [RTI Issue ID ROUTING-1024]