2.2.7. RTI Infrastructure Services¶
184.108.40.206. RTI Routing Service¶
220.127.116.11.1. Periodic event now configurable individually per Route¶
A periodic event can now be individually enabled and configured for each Route as follows:
<route> <periodic_action> <sec>0</sec> <nanosec>400000000</nanosec> </periodic_action> </route>
This setting overrides the one specified in the
<session> tag is still supported and allows you to define a default value for
all contained routes.
The new functionality has also been applied to the Processor API, so the
Route::period() operation only affects the Route object and not the parent Session.
Make sure your application is updated accordingly if these changes affect it.
18.104.22.168.3. Known issues¶
22.214.171.124.3.1. Attempting to route builtin Security Logging Topic or Monitoring Library Topics causes Routing Service crash¶
Routing the Security Logging builtin Topic (
DDS:Security:LogTopic) or the
Monitoring Library Topics causes a crash if any of the participants involved in
the route have security logging enabled (i.e., the property
com.rti.serv.secure.logging.distribute.enable is set to true) or they are
configured to publish the Monitoring Library Topics in the same domain
rti.monitor.config.new_participant_domain_ id property is set).
Note that you can enable security logging and use the Monitoring Library on participants that talk to Routing Service, and even route these Topics. This problem occurs only if the Routing Service participant itself is publishing samples on these Topics.
[RTI Issue ID ROUTING-727]
126.96.36.199.3.2. Unbounded memory growth when restarting Service or creating/deleting DomainRoutes¶
When using Routing Service as a library, starting and stopping Routing Service instances within the same process may lead to an unbounded memory growth with a small memory increment every time an instance is stopped.
Creating and deleting DomainRoutes within a Routing Service instance may also lead to an unbounded memory growth with a small memory increment every time a DomainRoute is deleted.
[RTI Issue ID ROUTING-833]
188.8.131.52. RTI Recording Service¶
184.108.40.206.1. Files table extended¶
Previously, Recording Service used the ‘Files’ table to hold all information about the recorded user files. (‘Files’ is an internal table that Recording Service uses to replay the recorded database.) In 6.1.0, this internal table has been updated to also contain the maximum and minimum source timestamp. To not lose compatibility with 6.0.1, this internal table has been renamed ‘Files_2_0.’
Therefore, the first time that you replay a 6.0.1 database using Replay Service 6.1.0, the replay will need some time to create the ‘Files_2_0’ table and calculate the maximum and minimum source timestamp of each file. The size of the metadata file can also grow.
220.127.116.11.2. Instance History Replay¶
The new Instance History Replay feature requires some new tables in order to store the custom instance history index. These tables are required in order to calculate the state of the world efficiently.
The first time that you replay a 6.0.1 recorded database with this feature enabled, the Replay Service will need significant time to index the tables. Also, the size of the database will grow due to the creation of the new tables.
18.104.22.168. RTI Persistence Service¶
22.214.171.124.1. Incompatible Persistent Storage (Database) Format¶
In 6.1.0, the schema of the persistent storage files and tables created by Persistence Service to store DDS samples and instances has changed. Therefore, you cannot use the files and/or tables generated with previous releases of Persistence Service with Connext 6.1.0.
If you have this requirement, contact RTI Support at firstname.lastname@example.org.