RTI Recording Service 5.1 Release Notes
Contents
1. What s New in 5 1 0 New Platforms This release adds support for the following platforms CentOS and Red Hat Enterprise Linux 6 2 6 4 L SUSE Linux Enterprise Server 11 SP2 x86 3 x kernel J Ubuntu Server 12 04 LTS LI Windows 8 32 bit and 64 bit Editions Windows Server 2012 R2 64 bit Edition 1 To support compatibility with 4 2e please see the RTI Core Libraries and Utilities Release Notes What s New in 5 1 0 4 2 4 2 1 4 2 2 4 2 3 4 3 4 3 1 4 3 2 4 3 3 4 3 4 Extensible Type Support Support for Mutable Types This release includes support for mutable types as defined in the Extensible and Dynamic Topic Types for DDS DDS XTypes specification from the Object Management Group OMG Starting with this release Recording Service can record and replay topics where the underlying types are mutable Support for Optional Types This release adds support for optional members as defined in the Extensible and Dynamic Topic Types for DDS DDS XTypes specification from the Object Management Group OMC Starting with this release the Record and Replay tools can work with topics whose underlying types have optional members Extensible Type Directives Added to Recorder and Replay IDL Files The IDL definitions for the remote administration of Record and Replay tools have been updated to make use of the new Extensible Types capabilities Improvements to Recording Console New Behavior when Usi2. RTI Recorder started exception RTIDRTUserDataTable update 678 near syntax error exception RTIDRTUserDataTable new 957 Table update exception RTIDRTUserDataReader_new 896 Failed to create user subscription exception RTIDRTUserDataSubscriber_create_datareader 276 Failed to cre ate reader exception RTIDRTUserDataSubscriber_add_reader 317 Failed to create reader exception RTIDRTUserDataEvent process 164 Failed to add data reader What s Fixed in 5 1 0 5 2 5 2 1 5 2 2 exception RTIDRTDataBase begin transaction983 error locking DB cannot start a transaction within a transaction exception RTIDRTDataBase begin transaction 83 error locking DB cannot start a transaction within a transaction The process became unresponsive to normal termination and had to be killed This problem has been resolved RTI Issue ID RECORD 340 Problems Recording Multiple Versions of Type in Serialized Format Recording in serialized format when multiple versions of a type were available extensible extensibility was not working properly The tables may have been mistakenly recorded in dese rialized format This problem has been resolved There is a known limitation when DataWriters do not publish typecodes see Known Issues Sec tion 6 RTI Issue ID RECORD 343 After Remote Command to Reconfigure with auto_start Set to True Recording Failed to Start Automatically When reconfiguring the Record tool to use a
3. used by the user These names have been added to the IDL COMMAND_REQUEST_TOPIC_NAME and COMMAND_RESPONSE_TOPIC_NAME Association of XML Type Definitions with Topics This release includes a new configuration tag called lt topics gt within lt type gt You can use it to make an explicit association between Topics and XML type definitions For example lt type gt lt element gt register top levelstrue lt register top level type name CanonicalTypeName type name gt topics lt element gt TopicName lt element gt lt topics gt lt element gt lt type gt For more information see Section 4 10 and Section 7 10 in the Recording Service User s Manual Ability to Select XML Type to be Registered Based on Topic Name The Record and Replay tools now allow you to specify lists of topics associated with the type def initions in the XML files What s New in 5 1 0 4 4 12 4 4 13 4 4 14 4 5 4 5 1 4 5 2 A new XML configuration tag topics has been addded to the Type Registration properties in both the Record and Replay tools The type configuration settings now have this format type elements register top level true register top level type name gt CanonicalTypeName lt type name gt lt topics gt lt element gt TopicName lt element gt lt topics gt lt element gt lt type gt You can use the new lt topics gt tag to specify lists of topics names or regular e
4. path separator is automat ically read from the metatable data What s New in 5 1 0 4 4 4 4 4 5 4 4 6 4 4 7 Ability to Change Record Tool s Partition QoS For each Record Group in the XML configuration Recording Service creates a DDS Subscriber There is one Subscriber in each of the Record Group s domains This release adds a way to change the Partition QoS setting for these Subscribers For instance suppose the Record tool needs to record data from producers that are organized into different partitions based on their geographical distribution different locations are repre sented by different Partition strings You can specify a Partition QoS policy via XML configura tion when the Record tool starts up But suppose the data producers change location and thus change their Partition QoS To keep recording the data the Record tool needs to change its Parti tion QoS too Starting with this release you can change the Partition QoS for any or all Record Groups by using the new RII REMOTECTX MSG RECORDER PARTITION message type See the updated RTI Recording Service User s Manual Section 5 3 1 for more information Ability to Specify SQLite PRAGMA Statements to Execute Before Table Creation Recording Service now includes the ability to specify SQLite pragma statements to be executed right after the database file is created and before any table or data is inserted Pragmas are spec ified using the new lt sqlite_pragmas g
5. reversed so that the most natural choice Create File appears on the right Ability to Drag and Drop Files To select a configuration file or a recording file you can continue to use the old method of browsing to a folder and selecting a file or you can simply drag and drop the desired file onto the Console s panels What s New in 5 1 0 4 3 5 4 4 4 4 1 4 4 2 4 4 3 Improved Configuration Mode Selector The icon for selecting a configuration mode in Recording Console has been changed to a drop down menu from which you can choose whether or not to use an external configuration file Other Improvements and Features Ability to Select What Samplelnfo Metadata and Discovery Fields to Store in Recorded Databases The Record tool now includes the ability to filter in or out the Sample Info discovery or metadata fields to be recorded Fields can be specified by using the name or by using regular expressions to group them This allows you to save space in the recorded databases which improves resource utilization In addition the default set of recorded fields has been modified In previous versions of the tool all Sample Info discovery and metadata fields were stored in the database along with the user data samples Starting with this version only the fields required for the recorded databases to be compatible with the Replay and Converter tools are recorded if no specific field filters are speci fied See the Recordin
6. 01 57 647 Thread 16 This problem has been resolved What s Fixed in 5 1 0 5 3 3 5 3 4 5 3 5 5 3 6 RTI Issue ID RECORD 369 Slow Start up for Console In the previous release it took a long time for the Console to start up This problem has been resolved RTI Issue ID RECORD 169 Console Hung While Launching Record or Replay if NDDS DISCOVERY PEERS Excluded Local Discovery The Console would hang and display Launching after clicking on the Record or Replay but tons This occurred on systems configured with the NDDS DISCOVERY PEERS environment variable set in a way that prevented local discovery e g not including shared memory and not including localhost or any other such option thus affecting the QoS used for communication between the Console and the Record or Replay tools preventing them from discovering each other The Console Record and Replay tools always run on the same machine The Console launches and configures the Record or Replay tools and in particular configures the communication QoS between the tools and the Console The configuration provided by the Console in the previous release did not account for the case mentioned above In this release the administration domain used by the Console and the Record Replay tools to intercommunicate is explicitly configured by the Console to set initial peers to shared memory thus overriding and preventing any other value for this attribute wheth
7. Dri dtes 10 5 2 6 Dynamic DataReader Failed to Deserialize Mutable Sample Published by Replay Service DataVV rep ott e eet tete cinch seven e E Ie E ree er Toce e ers 10 5 27 Indexes not Created in Database Segments sssssssssssssssssseeeeeenene 10 5 3 Fixes Related to Recording Consoles ssie ieres a aans roana eren nennen 10 5 3 1 Recording Console Log Files not Removed esses 10 5 3 2 Failure to Record or Replay from Console when Type Information Provided via XML 10 5 3 3 Slow Start up for Console usines Ree eie ii ea cre their there 11 5 3 4 Console Hung While Launching Record or Replay if NDDS DISCOVERY PEERS Excl ded Local Discovery een nete eet Hier ree ee dar de Ie 11 5 3 5 Issues with Synchronized Control and State Indication between Console and System Tray 1cOn E X 11 5 3 6 No Indication of Why Replay was Disabled when Recording File was Empty 11 5 3 7 Improved Response Time for Opening Settings Panel 12 5 3 8 Crash in Recording Console when Changing Replay or Recorder Domain ID while Slacira pA CER 12 5 3 9 Possible Recording Console Frozen Status eene 12 5 3 10 Recording Console Appeared Unresponsive if Deprecated Tag used in Configuration Tiles tin Ice n Le I ME 12 5 3 11 Error from Recording Console when Using domain type config Property 12 54 Fixes Related t0 Converter side e ranae en RE DP o
8. ML name tag under administration Admin Console will not recognize the replay service and will not be able to administer it This will be addressed in a future release RTI Issue ID BIGPINE 429 6 2 Issues Related to Recording Console d d d d d In Recording Console when changing playback speed or skipping to another playback location occasionally playback will appear stuck it is actually paused The workaround is to click the Pause button twice Recording Console may fail to shut down gracefully after stepping through to the end of a recording If a recording is paused and then stepped through to the end the Replay ser vice may not shut down properly In this case Recording Console displays an error that the service stopped unexpectedly RTI Issue ID RECORD 135 Interaction between Recording Console and Admin Console This issue only applies if you are using Recording Console and RTI Admin Console at the same time and you have configured Admin Console to join domain ID 99 In this scenario do not use Admin Console to pause or disable any Recording Console services their names begin with RTI Recorder or RTI Replay Doing so may cause an error in Recording Console RTI Issue ID BIGPINE 795 Recording Console will not reflect stopped status if recording is stopped by another tool When recording data with Recording Console RTI Admin Console can send a command to stop the recording In this case record
9. RADEON OI RME MA DA 2 AN New PlAttOrins e m 2 42 Extensible Type Suppott eacesuacetemecmau eaae ihoneieliun edi deni ied 3 42 1 Support for M table Types emm iaa eraitera aaae Ra eitas 3 422 Support for Optional Types iiec ecciesie i rhe ir eia rais 3 4 23 Extensible Type Directives Added to Recorder and Replay IDL Files 3 43 Improvements to Recording Console sse nennen eene nennen nennen 3 43 1 New Behavior when Using Console s Pause and Restart Buttons ssssssssss 3 4 32 New Behavior for Record Button when Recording is Paused sss 3 4 3 3 Changes to Console s Dialog to Create Recording File sss 3 434 Ability to Drag and Drop Files tete ree pe e ie pedet ring 3 43 5 Improved Configuration Mode Selector cccsccccsescssssescsnsnessesesneesescecenessscsnsnsnesesesescsescananens 4 44 Other Improvements and Features assii estende d i iren ha t ddr deas re dua eate 4 44 1 Ability to Select What SampleInfo Metadata and Discovery Fields to Store in Recorded Databases innishecuiiemeoeiname otiam nom miden iia iei 4 44 2 Ability to Configure Replay to Use a Non Default Path Separator sss 4 4 4 3 Replay and Recording Console Now Autodetect Path Separator from Recorded Database 4 44 4 Ability to Change Record Tool s Partition QoS cccccccccc
10. RII Recording Service Release Notes Version 5 1 0 f t Your systems Working as one 2013 Real Time Innovations Inc All rights reserved Printed in U S A First printing December 2013 Trademarks Real Time Innovations RTL and Connext are trademarks or registered trademarks of Real Time Innovations Inc All other trademarks used in this document are the property of their respective owners COPY and Use Restrictions ur of this publication may be reproduced stored in a retrieval system or transmitted in any form including electronic mechanical photocopy and facsimile without the e written permission of Real Time Innovations Inc The software described in this dune is furnished under and subject to the RTI software license agreement The software may be used or copied only under the terms of the license agreement Technical Support Real Time Innovations Inc 232 E Java Drive Sunnyvale CA 94089 Phone 408 990 7444 Email supportGrti com Website https support rti com Contents CHE eirauri ce 1 2 Additional Libraries Needed on Select 64 Bit Platforms eee 1 3 Compatibility with Other RTI Products eere reete tenete tete tntn tata tntnnnun 1 3 1 Command Line Options Compatibility sssssssssseeseseeeeneerenene EENE EENE ennt 2 4 Whats New 15 LU scoop desino ded ane UR RO EIN OR RR ESSE LENIN LR ERIS EMEMR
11. age size max for the UDPv4 UDPv6 TCP Secure WAN and shared memory transports changed to provide better out of the box perfor mance Recording Service 5 1 0 also uses the new default value for message size max Consequently Recording Service 5 1 0 is not out of the box compatible with applications running older versions of Connext or RTI Data Distribution Service Please see the RTI Core Libraries and Utiltities Release Notes for instructions on how to resolve this compatibility issue with older Connext and RTI Data Distribution Service applications l Some changes have been made to the Record and Replay IDL files See Section 4 4 9 1 The types of the remote administration and monitoring topics in 5 1 0 are not compatible with 5 0 0 Therefore e The 5 0 0 Record and Replay shells Admin Console 5 0 0 and Connext 5 0 0 user appli cations performing monitoring administration are not compatible with Recording Service 5 1 0 e The 5 1 0 Record and Replay shells Admin Console 5 1 0 and Connext 5 1 0 user appli cations performing monitoring administration are not compatible with Recording Service 5 0 0 Command Line Options Compatibility Starting with Release 5 1 0 the Replay tool s command line parameter forceXmlTypes is deprecated The XML type configuration will always be used if it is available For details on how the Replay tool selects a type definition for a Topic see Section 7 10 in the Recording Service User s Manual
12. and store indexes rather than depend upon automatic indexing for the tables which it will be replaying saving initialization time on subsequent replays The Replay tool s ability to store indices is controlled by the lt readonly gt parameter of the replay database Setting lt readonly gt to true prevents Replay from storing indices for a table in this mode the Replay tool will display a message during initialization for each table opened stating that it was unable to store the table index Setting lt readonly gt to false the default will allow the Replay tool to write the table indices to the database The Replay tool s performance is not affected by this option it will use the fastest means of retrieving samples in either case But setting the lt readonly gt option to false may help improve the tool s initialization performance When loading a large file for playback please be aware that this operation may take some time LI If you load the configuration file examples replay simple config xml and select the fast replay configuration profile while using your own recorded data file instead of the example recording from RTI the Replay service will exit and log a message regarding no match in the recording for A Topic Known Issues d d The Record and Replay Shells are not completely compatible with standard input piping of commands For RTI Admin Console to work properly with the Replay tool do not use the X
13. atabase Access to Locate Table sss 8 5 1 3 Record Tool Locked First Segment in Set Throughout Whole Operation Time 8 5 1 4 Wrong Column Limit in Recorded Deserialized Format esses 8 5 15 Issues in XSD Definitions for Recorder sess tenentes 8 5 16 Recording Failed when shared table Set to True sss eee 8 5 17 Problems Recording Multiple Versions of Type in Serialized Format 9 5 1 8 After Remote Command to Reconfigure with auto start Set to True Recording Failed to Start Automatically eterne dero torrente dias ceris aati 9 5 19 Unable to Record to Database if File Name Contained non ASCII UTF 8 Characters e g Arabic Windows Platforms Only eee eee eene 9 5 27 Fixes Related to Replay LOO icc dette ciento eere ee ete e re Ht E re deer te innere oda 9 5 21 Ability to Configure Replay to Use a Non Default Path Separator sss 9 5 22 Replay Wrote Invalid Samples from Database sss eee 9 5 23 Corrupted Typecodes from Replay Service sssssssssssssssseeeneeeenenn 10 5 24 Replaying Same Database File from Multiple Database Entities in Recording Service Failed with database is locked Error sesenta 10 5 25 Failure to Replay Topics Recorded with no TypeCode Information in DCPSPublication Table t tr trend le e oS eee quera eere aie
14. configuration in which auto start was set to true recording did not start automatically as expected This problem hasn been resolved RTI Issue ID RECORD 350 Unable to Record to Database if File Name Contained non ASCII UTF 8 Characters e g Arabic Windows Platforms Only On Windows platforms only Recording Service failed to record to a database file if the file s name contained non ASCII UTF 8 characters such as Arabic The database files were created correctly but no user data was recorded into them This problem has been resolved RTI Issue ID RECORD 511 Fixes Related to Replay Tool Ability to Configure Replay to Use a Non Default Path Separator SOLite tables created by the recording service have table names constructed from the topic name record group name and domain name separated by a path separator character The Record and Replay tools use the character as the default path separator character but while the Record tool could be configured to use a different character the Replay tool could not This deficiency has been corrected Now you may specify the path separator character for each replay database entity using the XML path separator tag The path separator may be any character except and 7 These are the same characters restricted by the Record tool However when using non default path separators you must ensure that the path separator character is unique i e not used in any t
15. converted string is larger than the maxi mum the number will be converted using scientific notation RII Issue ID RECORD 537 Converter Failed to Work Properly with Wide Strings Converter was not working properly with wide string types resulting in incomplete strings in the converted files or even exceptions in the serialized case This problem has been resolved RTI Issue ID RECORD 542 Known Issues Issues Related to Replay Tool 1 The Replay tool currently does not support the following XML configuration modes replay service auto exit has no effect replay topic output lt keyed gt has no effect time control start mode MATCHED or LOOP modes time control rate AS FAST AS POSSIBLE except for session level topic time control start mode MATCHED mode Limitations with the Replay tool s shell commands e The step command is functional for session and topic entities only not service or database e The rate command is functional for topic entities only 1 Performance and indexing with the Replay tool The Replay tool replays stored samples in the same order in which they were received using SQLite indexes to retrieve the samples in sorted order SQLite automatically builds indexes when opening an SQLite table for sorted access for large tables the process of building the index may take some time To improve initialization performance the Replay tool attempts to create
16. d Hat Enterprise Linux 5 or 6 64 bit platform you will need to install a set of 32 bit libraries before installing Recording Service d On Red Hat Enterprise Linux 5 and 6 64 bit platforms run this command all on one line you will need root permission yum install glibc i686 1ibX11 1686 gtk2 i686 libXtst i686 ncurses libs i686 PackageKit gtk module i686 libcanberra gtk2 i686 L On Ubuntu 64 bit platforms run this command you will need root permission apt get install libc6 ia32 libs multiarch 3 Compatibility with Other RTI Products The Record tool supports the standard Connext transports UDPv4 UDPv6 and shared mem ory as well as the RTI Secure WAN Transport plugins Recording Service 5 1 0 is compatible with RTI Connext 5 0 0 and higher as well as RTI Data Distri bution Service 4 5 b f 4 4d 4 4b 4 3e and 4 2e except as noted below What s New in 5 1 0 3 1 LI Recording Service 5 1 0 is not backwards compatible with databases recorded with previ ous releases of RTI Recording Service This applies to all the tools in Recording Service Record Replay Converter and Recording Console LI Recording Service is not compatible with applications built with RTI Data Distribution Ser vice 4 5e and earlier releases when communicating over shared memory For more infor mation please see the Transport Compatibility section in the RTI Core Libraries and Utilities Release Notes 1 In Connext 5 1 0 the default mess
17. ecording Service and Converter cannot deserialize bit fields If this type is used the dese rialize mode must be RIIDDS DESERIALIZEMODE NEVER 1 If the Connext application being recorded has a keyed data type and DataWriterProto colOosPolicy disable inline keyhash is set to TRUE not the default Recording Service may misinterpret samples as being from the wrong instance 1 If you start an instance of the Record tool using command line options not a configura tion file then sending a new configuration to that instance of the Record tool using the remote shell will not work L When time mode is set to TOPIC RELATIVE the first sample in a recording is not sent right away when replay starts RTI Issue ID RECORD 133 1 There is a known limitation when recording data in serialized format in environments where multiple versions of a type are published If the writers do not publish their type code information the Record tool may store samples from unwanted versions RTI Issue ID RECORD 346 L On Windows 8 systems be aware of a limitation in the OS regarding the write permis sions in some folders Even if you are using an administrator account some folders such as C or Program Files cannot be used to store user data If you try to create a recording database there Windows 8 will automatically create it in a virtual storage unit usually found under C NUsersN user name NAppDataNLocalNVisualStore This folder might be
18. er by a configuration file or environment variable This change will only affect the domain used by the Console and the Record Replay tools to com municate domain 99 by default it will have no effect on any other domain that the service con nects to RII Issue ID RECORD 344 Issues with Synchronized Control and State Indication between Console and System Tray Icon When controlling Administration Console from the system tray icon with a right click or when the console would perform a scheduled operation the state indication in the console would not update appropriately For instance when a scheduled replay operation would begin the UI LCD would turn green but the replay button would not light up since it was not clicked on This release improves the state indication to indicate the state in the same way no matter what triggers the console state change Such triggers include controlling the console from the system tray icon right click the scheduler or even by changing the service state of the service associ ated with the console by the Administration Console RTI Issue IDs RECORD 323 RECORD 343 RECORD 352 No Indication of Why Replay was Disabled when Recording File was Empty When loading an empty recording file there was no indication of why the Replay button was disabled on the Console This problem has been resolved If the loaded recording file is empty Replay will be disabled and the settings panel will sho
19. following sequence of operations will fail because m2 is assigned before m1 and has a length greater than 65535 characters str DDS String alloc 131072 memset str x 131072 str 131071 0 DDS DynamicData set string data m2 DDS DYNAMIC DATA MEMBER ID UNSPECIFIED str DDS DynamicData set string data ml DDS DYNAMIC DATA MEMBER ID UNSPECIFIED str If the member m1 is assigned before m2 the sequence of operations will succeed RTI Issue ID CORE 3791 1 RTI does not recommend using files that are mounted over NFS to store recorded data Recording Service uses file locking which has known issues working over NFS If file locking is not working Recording Service will hang In particular this problem may appear on Yellow Dog Linux systems 1 Leading and trailing spaces in a Topic Name are ignored However spaces within the string are allowed For example My Topic will be treated as My Topic 15 Known Issues Fully qualified field names in struct s cannot be longer than 1 024 characters l Sequence and array indices cannot be used in Topic or Field expressions 1 Recording Service cannot communicate with DataReaders or DataWriters of Topics with a data type that includes bit fields You may see the following message but Recording Ser vice will continue to work normally otherwise DDS DynamicDataTypeSupport initialize type not supported bitfield member RTI Issue ID CORE 3949 1 R
20. g Service User s Manual for details There is also a new boolean flag in the XML configuration replay compatibility that can be used When set to true this new flag ensures that the necessary fields for Replay and Converter to work are always preserved regardless of what the field filters are Ability to Configure Replay to Use a Non Default Path Separator SQLite tables created by Recording Service have table names constructed from the topic name record group name and domain name separated by a path separator character The Record and Replay tools use the character as the default path separator character but while the Record tool could be configured to use a different character the Replay tool could not This defi ciency has been corrected Now you may specify the path separator character for each replay database entity using the XML path separator tag The path separator may be any character except and 7 These are the same characters restricted by the Record tool However when using non default path separators you must ensure that the path separator character is unique i e not used in any topic name record group name or domain name Failure to ensure the uniqueness of the path separator character will most likely cause the Replay tool to fail Replay and Recording Console Now Autodetect Path Separator from Recorded Database When a database is loaded by the Replay tool or Recording Console the
21. hidden RTI Issue ID RECORD 525
22. ify DataReader or DataWriter settings in the Record or Replay configurations the topic name is still matched against any topic filters defined in the default QoS settings e g in the USER QOS PROFILES xml file This is new behavior for both Record and Replay Recording Service Administration Database Info Type Changed The RTIRecorderDatabaseInfo type in the Recording Service administration IDL file rtire cord idl has changed it now uses 64 bit integers for the received and saved byte counts The new type is defined as follows struct RTIRecorderDatabaseInfo unsigned long long received_bytes unsigned long long saved_bytes i3 Important This change introduces an incompatibility between old versions of the IDL file and this one Changes in Record and Replay IDL Files Some changes have been made to the Record and Replay IDL files J In the Record IDL file resource idl rtirecord idl The topic names for administration have been changed so that they are better aligned with other RTI components e The command request topic name is now rti recorder administration command request The command request status topic name is now rti recorder administration command response e Some type names and enumeration values in the IDL have been changed so they are more representative J In the Replay IDL file resource idl rtireplay idl The topic names did not have string constants in the IDL file that could be accessed and
23. ing will stop but Recording Console won t reflect the stopped status in any way it will appear that recording is still in progress although the file won t grow in size Pause commands work fine and are reflected by both sides Recording Console and Admin Console RTI Issue ID RECORD 253 Welcome screen may appear blank on some platforms The welcome screen may appear blank if the operating system does not have a web browser that is compatible with Eclipse RTI Issue ID DIABLO 538 6 3 Issues Related to Converter d d d When using Converter on a recording created with Recording Console you may see a warning related to internal topics used by the Console exception RTIConverterModel PublisherCallback 2293 Failed to create type com rti tools remotectx You can safely ignore the warning the conversion results are valid Converter rtirecconv cannot convert tables with only a subset of the data In general if you record in deserialized mode use the sqlite3 command to convert to HTML and CSV if you record in serialized mode use Converter In files recorded on Windows systems the recorded timestamp is the number of micro seconds since the device was booted not since January 1 1970 Therefore the time gmt option to Converter rtirecconv will not show the correct time Known Issues 6 4 Other Issues J When you record a database using the PRAGMA feature lt sqlite_pragmas gt in the recorder database sett
24. ings the resulting databases may be incompatible with Record ing Console This is due to a third party incompatibility The following exception will be thrown java sql SQLException file is encrypted or is not a database To replay the database use the Replay tool RTI Issue ID RECORD 574 1 Recording and or replaying mutable types requires the type definition to be provided via XML configuration using the type config tag If the type definition is not provided via XML the Record tool will display the following error messages When recording in deserialized mode Failed to get valid typecode information for Publisher Recorder cannot confirm that the entity publishes a supported type When recording in serialized mode DDS DynamicData from stream ERROR Bad parameter encapsulation kind of stream I To record a data type that has more than 5 050 primitive types you must set the deserialize mode property to RTIDDS DESERIALIZEMODE NEVER Otherwise you will see the following error message and recording will fail exception RTIDRTUserDataTable update 610 too many SOL variables RTI Issue ID RECORD 38 J The DynamicData API does not support out of order assignment of members with a length greater than 65 535 bytes In this situation the following error is reported sparsely stored member exceeds 65535 bytes For example struct MyStruct string lt 131072 gt ml string lt 131072 gt m2 With the above type the
25. ions Replay Tool s Command Line Option noAutoEnable no Longer Available The Replay tool s command line option noAutoEnable has been removed It cannot be sup ported because the enable disable remote administration commands are not supported The self contained Option Deprecated With the new field selection capabilities the self contained option in the Recorder Database properties has been rendered obsolete and starting this version it is considered deprecated When the new replay compatibility option is active all the necessary fields in the necessary tables will be propagated to new segments as they are created What s Fixed in 5 1 0 5 1 5 1 1 5 1 3 What s Fixed in 5 1 0 Fixes Related to Record Tool Source and Reception Timestamps Recorded Differently Although the Sample Info source timestamp and reception timestamp fields were of the same type the Record tool recorded them differently Source timestamps were stored in two separate numeric columns while reception timestamps were recorded as text This problem has been resolved Now both fields are recorded the same way one single numeric column representing nanoseconds RTI Issue ID RECORD 43 Record Tool used Inefficient Database Access to Locate Table When the Record tool discovers a new DataWriter for a topic it checks for the existence of a table associated with the topic In the previous release it checked for the table in an inefficien
26. ng Console s Pause and Restart Buttons The behavior of some of the buttons on the Console have changed 1 When using the Console to replay data at a non default speed pressing Pause and then Play will resume replay with no change to the replay rate In the previous release replay would have changed to the default rate 1 If you press the Fast Forward button after pausing replay this action replays at a higher rate while the button is pressed and then release the button replay will go back to a paused state In the previous release replay would have continued at a normal rate 1 If you pause recording and then press Record recording will resume In the previous release clicking on the record button in this state would prompt the user to acknowledge restarting the recording New Behavior for Record Button when Recording is Paused In previous releases if you paused recording and then clicked on the Record button the Console would prompt and ask if it should restart the recording and record over the file In this release the Console s interface has been slightly changed when paused Now if you click on the Record button while paused it will resume recording just as if you clicked on the Pause Resume button Changes to Console s Dialog to Create Recording File The dialog that is used to create a recording file has been changed slightly The position of the two buttons on the bottom to either Discard or Create File have been
27. onfiguration Replay was unable to replay and would exit This problem has been resolved RTI Issue ID RECORD 334 Dynamic DataReader Failed to Deserialize Mutable Sample Published by Replay Service DataWriter A Dynamic DataReader failed to deserialize a mutable sample published by a Replay service DataWriter The issue only occurred when samples were recorded in serialized mode This prob lem has been resolved RTI Issue ID RECORD 364 Indexes not Created in Database Segments When a new database segment was created indexes were created for the first segment but they were not in the subsequent ones This problem has been resolved RTI Issue ID RECORD 552 Fixes Related to Recording Console Recording Console Log Files not Removed The log file created by Recording Console was not deleted after the application exited This prob lem has been resolved now log files will be removed if no problems were encountered during application execution RTI Issue ID RECORD 365 Failure to Record or Replay from Console when Type Information Provided via XML Recording Console could not start the Record or Replay tools when the input configuration pro vided the type definitions through XML using the tag type config The log files generated by Recording Console showed an error like the following INFO recording service stdout exception RTIDRT XmlTypeConfiguration read config09864 Failed to read type configu ration 2012 12 13 16
28. opic name record group name or domain name Failure to ensure the uniqueness of the path separator character will most likely cause the Replay tool to fail RTI Issue ID RECORD 199 Replay Wrote Invalid Samples from Database The Replay tool did not take into account the invalid data flag in recorded Sample Info fields and published repeated consecutive samples This problem has been resolved RTI Issue ID RECORD 290 What s Fixed in 5 1 0 5 2 3 5 2 4 5 2 5 5 2 6 5 2 7 5 3 5 3 1 5 3 2 Corrupted Typecodes from Replay Service The Replay tool corrupted typecodes sent on the wire when replaying databases stored in serial ized mode and when the typecode was taken from the DCPSPublication table This problem has been resolved RTI Issue ID RECORD 291 Replaying Same Database File from Multiple Database Entities in Recording Service Failed with database is locked Error Attempting to replay the same database file from multiple entities with lt readonly gt set to false and no preexisting indexes in the file would result in a database is locked error and Replay would fail This problem has been resolved RTI Issue ID RECORD 318 Failure to Replay Topics Recorded with no TypeCode Information in DCPSPublication Table The Replay tool failed to replay data that was recorded without TypeCode information stored in the DCPSPublication table in the database file Even if the types were provided via XML type c
29. sesesteesceseseseecensesesesnesesesceeesesssnenananens 5 44 5 Ability to Specify SQLite PRAGMA Statements to Execute Before Table Creation 5 44 6 Improved Exporting of Sequences and Arrays of Octets in Converter 5 4 4 7 Record and Replay now Include Support for QoS Topic Filters sss 5 44 8 Recording Service Administration Database Info Type Changed 6 4 4 9 Changes in Record and Replay IDL Files sse nenne nnns 6 4 4 10 Association of XML Type Definitions with Topics ssssssssssseeeeneeereneee 6 44 11 Ability to Select XML Type to be Registered Based on Topic Name 6 4 4 12 Updated to SQLite Version 3 7 17 sse nennen nnne nennen 7 44 13 Increased Error Level for Incompatible QoS Error Messages sese 7 4 4 14 Increased to Exception Level All Error Messages that Cause Types not to be Recorded 7 45 Removed Deprecated Options eet eem idee Hine eer n eH ve y 45 1 Replay Tool s Command Line Option noAutoEnable no Longer Available 7 4 5 2 The self contained Option Deprecated sse eee ee een e nnns 7 5 Whats Fixed m 5 L Orioren Sei vati cognate vb Uim a RERO ecd di cipia eril bu dua tat 8 bil pixes Relatedto Record lOO 2 eet tie repete eerte te e eee rete 8 5 1 1 Source and Reception Timestamps Recorded Differently sssssssssssss 8 5 12 Record Tool used Inefficient D
30. t XML setting included in the recorder database set tings This new feature can be used for example to change the page size on Windows systems for bet ter efficiency or to change the journal mode settings to use Write Ahead Logging WAL mode for improved concurrent access to the database while recording Improved Exporting of Sequences and Arrays of Octets in Converter The way sequences and arrays of octets and characters are exported has been improved in Con verter Bytes are now shown as their uppercase hex representation and different bytes are sepa rated by dashes e g FA 05 5B Record and Replay now Include Support for QoS Topic Filters This release supports setting topic filters in the QoS settings for the Record and Replay tools When defining DataReader QoS settings in the Record tool s configuration you can specify a topic filter in the Topic Group settings For example topic group name TopicGroup gt datareader qos topic filter Topicl1 gt datareader qos topic group The same applies to Replay s DataWriter QoS settings within the output settings of the replay topic section For example replay topic output datawriter qos topic filter Topicl gt datawriter qos output replay topic For information on topic filters see the RTI Core Libraries and Utilities User s Manual What s New in 5 1 0 4 4 8 4 4 9 4 4 10 4 4 11 If you do not spec
31. t man ner which could take a long time if the table had a large number of rows This release uses a more efficient mechanism when searching for the table RTI Issue ID RECORD 387 Record Tool Locked First Segment in Set Throughout Whole Operation Time The Record tool locked the first file segment recorded in a multi segment session This was pre venting the user from for example moving or deleting it This problem has been resolved RTI Issue ID RECORD 401 Wrong Column Limit in Recorded Deserialized Format The User s Manual specified the column limit for recorded data to be 1 950 columns The tool actually supported just 999 user data columns In this release the column limit has been increased to 5 050 columns RTI Issue ID RECORD 402 Issues in XSD Definitions for Recorder Some of the example configuration files for the Record tool referred to an incorrect XSD filename rtirecorder xsd This caused some valid XML configurations to fail validation In this release all example configuration files refer to the correct XSD file rti_record xsd The XSD definitions that are used by the configuration can be found in the document resource schema rti_record xsd RTI Issue ID RECORD 303 Recording Failed when lt shared_table gt Set to True When a Topic Group in the Record tools s configuration had the lt shared_table gt tag set to true which is not the default the Record tool failed and logged the following errors
32. te ee ee be te iae 12 54 1 Converter was Missing Headers for Typedef Fields 12 5 4 2 Converter Failed to Properly Convert Databases Containing Types with Compact Array Ssi Mtas sch iU niacin adorare hotte n Benvenuti urn et 12 5 4 3 Segmentation Fault when Converting Very Long Double or Float Values 12 5 4 4 Converter Failed to Work Properly with Wide Strings sss eee 13 6 KNOWN BE 13 6 1 Issues Related to Replay Tool ccs nei dee oie AA Le od a eee de dee EE tede o rad 13 6 2 Issues Related to Recording Cos le sopsik ovsa haiei a nenne eene 14 6 3 Issues Related to Converter isoeo eiea ii aee ea aaa e aeiia 14 eR OthierI5S068 eroe AA AEE AEEA EAE E 15 Release Notes System Requirements RT Recording Service is supported on these platforms J Linux Platforms CentOS 5 4 5 5 6 0 6 2 6 4 e Fedora 12 e Red Hat Enterprise Linux 5 0 5 2 5 4 5 5 6 0 6 4 e SUSE Linux Enterprise Server 11 SP2 2 6 and 3 x kernel Ubuntu Server 12 04 LTS L All Windows platforms listed in the RTI Core Libraries and Utilities Release Notes with the same version number All 64 bit platforms run in 32 bit mode For more information on these platforms see the RTI Core Libraries and Utilities Release Notes and Platform Notes 2 Additional Libraries Needed on Select 64 Bit Platforms If you are installing Recording Service on an Ubuntu 64 bit platform or a Re
33. tion file This was due to the use of a XML property that is no longer available This problem has been resolved RTI Issue ID RECORD 563 Error from Recording Console when Using domain type config Property You may have seen an error when loading a recorder configuration file containing the property domain type config This was due to an error in the XSD file used by Recording Console when parsing the type definition file name This generated an exception that was found in the Record ing Console log This problem has been resolved RTI Issue ID RECORD 554 Fixes Related to Converter Converter was Missing Headers for Typedef Fields There was a problem when using Converter rtirecconv with types that contained typedefs The converted files had missing headers for the field names This problem has been resolved RTI Issue IDs RECORD 192 and RECORD 305 Converter Failed to Properly Convert Databases Containing Types with Compact Arrays Converter failed when converting tables for types that contained compact arrays of bytes or char acters This problem has been resolved RTI Issue ID RECORD 197 Segmentation Fault when Converting Very Long Double or Float Values Converter issued a segmentation fault when converting very large real values e g 1 0e310 This problem was due to the conversion format used to convert the number This format is now con Known Issues 5 4 4 ditional to the size of the resulting number When the
34. w that the file is empty RTI Issue ID RECORD 335 What s Fixed in 5 1 0 5 3 7 5 3 8 5 3 9 5 3 10 5 3 11 5 4 5 4 1 5 4 2 5 4 3 Improved Response Time for Opening Settings Panel In previous releases clicking on the button to open the settings panel would not respond instan taneously if Recording Console had been previously set to be configured with a file Responsive ness has been improved in this release RTI Issue ID RECORD 356 Crash in Recording Console when Changing Replay or Recorder Domain ID while Changing Views When changing the Replay or Record domain ID in Recording Console and quickly switching to another panel such as the Topics panel the application could have crashed if the domain ID change didn t complete before changing This problem has been resolved RTI Issue ID RECORD 403 Possible Recording Console Frozen Status When recording using Recording Console and loading an external configuration you may have seen Recording Console not update its status staying in the launching state This was due to a missing administration domain ID in the XML configuration Now Recording Console captures this case and adds a default administration domain ID RTI Issue ID RECORD 562 Recording Console Appeared Unresponsive if Deprecated Tag used in Configuration File You may have seen Recording Console remain in the launching state after it started recording with an external configura
35. xpressions If these topic names or regular expressions are discovered by the Record tool or are about to be replayed by the Replay tool they will use the type definition with the name specified by lt type_name gt Updated to SQLite Version 3 7 17 This release builds against an updated version of SQLite version 3 7 17 The change log for this version of SQLite is here http www sglite org releaselog 3 7 17 html For improved concurrency when accessing the SQLite databases generated by Recorder SQLite introduced the Write Ahead Logging WAL mode in version 3 7 0 WAL is not enabled by default in Recording Service but it can be used by setting it with the new pragma execution fea ture described in Section 4 4 5 Increased Error Level for Incompatible QoS Error Messages If an incompatible QoS error prevented Recorder Service from recording data an error message was shown with INFO level Now that message will be shown with a higher error level EXCEPTION Increased to Exception Level All Error Messages that Cause Types not to be Recorded In previous versions if Recording Service was not able to record data some error messages were shown with warning level You might have seen this issue when trying to record deserialized data that did not contain typecode information The error level for this kind of message has been increased to exception to make it more clear that your data will not be recorded Removed Deprecated Opt
Download Pdf Manuals
Related Search