14.4. What’s Fixed in 6.1.2

14.4.1. Type Containing Typedefs Caused INFO-Level Log Message about Different Type Definitions

If a type containing a typedef was provided to Routing Service through XML, the following INFO-level log message was printed when an endpoint using that type was discovered:

ROUTERDdsDiscovery_assertType:found two different type definitions with the same name=<user_topic_name>

This happened because, internally, Routing Service 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. Routing Service now uses the full type-definition, including typedefs, to compare with types found discovery.

[RTI Issue ID ROUTING-971]

14.4.2. Fourth Digit of Product Version not Logged at Startup

Routing Service did not log the fourth digit (revision) of the product version at startup. This issue has been resolved.

[RTI Issue ID ROUTING-975]

14.4.3. Stream-Query Propagation did not Work when Using More than One Session

When propagating stream-query result samples, Routing Service 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]

14.4.4. Samples Published Out of Order from Same Virtual GUID were Dropped

If Routing Service received samples for a given virtual GUID with sequence numbers that were out of order, Routing Service dropped samples with sequence numbers lower than the highest received sequence number. This issue has been resolved.

[RTI Issue ID ROUTING-928]

14.4.5. Routing Service Crashed if -maxObjectsPerThread Set Too Small

Routing Service crashed if the command-line option -maxObjectsPerThread had a value less than 1024. This issue, which also affected Recording Service, has been resolved. Now instead of crashing, the service will log a warning and the default value will be used:

Max objects per thread can't be lower than 1024. Setting MaxObjectsPerThread to 1024.

[RTI Issue ID ROUTING-1024]