7. Release Notes¶

7.1. Supported Platforms¶

RTI® Recording Service is supported on the platforms listed in Table 7.1.

It can also be deployed as a C++ library linked into your application. This is true for all platforms in Table 7.1 except SUSE® Linux® Enterprise Server 11.

Table 7.1 Supported Platforms in 6.0.0¶
Platform	Operating System
Linux	All Linux platforms in the RTI Connext DDS Core Libraries Release Notes with the same version number, except Ubuntu® LTS 16.04 on Arm® v8, NI Linux 3 on Arm v7, and Wind River® Linux 7. Not supported on any custom Linux target platforms.
OS X®	All OS X platforms in the RTI Connext DDS Core Libraries Release Notes with the same version number.
QNX®	Only supported on the custom target platform for QNX 6.6 on x86.
Windows®	All Windows® platforms in the RTI Connext DDS Core Libraries Release Notes with the same version number.

7.2. Compatibility¶

For backward compatibility information between Recording Service 6.0.0 and previous releases, please see the Migration Guide on the RTI Community portal.

7.3. What’s New in 6.0.0¶

Recording Service, Replay Service, and Converter are completely new in this release. They have been entirely rewritten, with these goals in mind:

Improving performance

Simplifying configuration

Becoming more consistent with other infrastructure services

Supporting new use cases

There are a few limitations compared to the prior version:

Does not support Recording Console, however, RTI Admin Console provides some of the functionality.
Does not yet support replaying in the original partition.
Does not include a remote shell application, but that is provided as an example.

7.3.1. Avoiding gaps in Replay when using time ranges¶

Replay Service used to extend the start timestamp to include relevant discovery data in the time range. While this allowed for the discovery of topics whose discovery events may have been out of the specified time range, it could also cause gaps when the discovery data and target data to be replayed were separated in time. To avoid these gaps, Replay Service no longer internally modifies the start timestamp defined by the user. All discovery data prior to the defined start timestamp will be discovered instantaneously.

7.4. What’s Fixed in 6.0.0¶

7.4.1. Pluggable storage for Converter discarded plugin properties specified in XML¶

When using the pluggable storage APIs with Converter, the properties passed to the plugin in the input_storage or output_storage tags (as shown below) were discarded. This problem has been resolved. Now the properties are passed to the plugin.

<input_storage>
    <plugin plugin_name="StorageLib::StoragePlugin">
        <property>
             <value>
                <element>
                    <name>MyProperty</name>
                    <value>MyPropertyValue</value>
                </element>
            </value>
        </property>
    </plugin>
</input_storage>

[RTI Issue ID RECNEXTGEN-412]

7.5. Known Issues¶

7.5.1. Recording Service may fail when current working directory in c:\Program Files¶

Recording Service will try to write to its database in the current working directory. If it does not have permissions to write there, it will fail with a confusing error:

[/recording_services/RecorderService|START|/storage|CREATE] create_connection:!SQLite - failed to open database file; sqlite returned error: out of memory
[SQLite return code = 7]
[File = metadata]

This happens most commonly when running the application from within c:\Program Files on Windows systems. You can work around this by running Recording Service from a command prompt in a directory where you have write permissions.