14.5. Previous Release

• 14.5.1. What’s new in 6.1.0
  • 14.5.1.1. New platforms
  • 14.5.1.2. Removed platforms
  • 14.5.1.3. Improved behavior if –verbosity set above the allowed maximum
  • 14.5.1.4. Service monitoring now reports CPU usage for individual Session threads
  • 14.5.1.5. Extended command-line parameter -verbosity to specify service and DDS verbosity independently
  • 14.5.1.6. New command-line option to save log in a file
  • 14.5.1.7. New message logging API, integrated with service logging system
  • 14.5.1.8. New APIs to get/set DynamicType from/in StreamInfo object
  • 14.5.1.9. Ability to define default values for variables in XML configuration
  • 14.5.1.10. Removed duplicate symbols in rtirsinfrastructure and rtiroutingservice libraries
  • 14.5.1.11. Enhanced logging information for each written sample
  • 14.5.1.12. Register type and content filter tags now consistent with DDS-XML specification
  • 14.5.1.13. Periodic event is now configurable individually per Route
  • 14.5.1.14. Added LoanedSamples::has_infos()
  • 14.5.1.15. New API to get a Route’s name, Route::full_name
  • 14.5.1.16. Increased verbosity for log message “ROUTERDdsConnection_assertType:two different type definitions…”
  • 14.5.1.17. Support for Input Transformation
  • 14.5.1.18. Several improvements in monitoring and administration infrastructure
  • 14.5.1.19. New XML element to wait for acknowledgment
  • 14.5.1.20. Ability to disable data on inputs event within routes/auto routes
• 14.5.2. What’s fixed in 6.1.0
  • 14.5.2.1. Operations expecting a string URL failed in Java Service-related APIs
  • 14.5.2.2. XML validation failed if allow/deny filter names in AutoRoutes contained whitespaces or new lines
  • 14.5.2.3. Routing Service crashed if monitoring participant creation failed
  • 14.5.2.4. Possible segmentation fault after failure to create Adapter Session, StreamReader, or StreamWriter
  • 14.5.2.5. Assertion failed while reading data from an Input on Windows platform
  • 14.5.2.6. -convertLegacyXml option failed on Windows systems if no output path specified
  • 14.5.2.7. Report of aggregated monitoring statistics contained invalid data
  • 14.5.2.8. Error re-enabling a route that was updated while disabled
  • 14.5.2.9. rtirssh crashed if load command was sent
  • 14.5.2.10. Unexpected “DDS_SqlTypeSupport_deserialize_Union:!deserializing union type” exception
  • 14.5.2.11. Crash when publishing a stream with different type names and using auto-route with monitoring
  • 14.5.2.12. Segmentation fault when attempting to enable a session with a disabled parent domain route
  • 14.5.2.13. QoS Profiles in NDDS_QOS_PROFILES.xml were not loaded
  • 14.5.2.14. Unnecessary network bandwidth for participant announcements generated by Routing Service