RTI Persistence Service Release Notes
Contents
1. Platforms Operating System Architecture Format 5AIX5 3xlc9 0 O AIX 5 3 No external database support es 19 0 Executable AIX 7 1 No external database support 64p7AIX7 1x1c12 1 jdk Executable INTEGRITY 10 0 2 F INTEGRITY Supports Transient Durability Mode onl pentiumInty10 0 2 pcx86 Library i86Linux2 6gcc4 1 2 jdk CentOS 5 4 5 5 2 6 kernel x64Linux2 6gcc4 1 2fjdk Executable CentOS 6 0 6 2 6 4 2 6 kernel i86Linux2 6gcc4 4 5 jdk Executable No external database support x64Linux2 6gcc4 4 5 jdk i86Linux2 6gcc4 1 1 jdk Red Hat Enterprise Linux 5 0 2 6 kernel x64Linwx2 6gcc4 1 1fjdk Executable Red Hat Enterprise Linux 5 1 5 2 5 4 5 5 i86Linux2 6gcc4 1 2 jdk Executable 2 6 kernel x64Linux2 6gcc4 1 2 jdk Linux Red Hat Enterprise Linux 6 0 6 4 2 6 kernel i86Linux2 6gcc4 4 5 jdk Executable No external database support x64Linux2 6gcc4 4 5 jdk ener Shere x64Linux2 6gcc4 3 4fjdk Executable 2 6 kernel SUSE Linux Enterprise Server 11 SP2 i86Linux3gcc4 3 4ljdk Exec table 3 x kernel Ubuntu Server 12 04 LTS 2 6 kernel i86Linux2 6gcc4 6 3 jdk Executable No external database support x64Linux2 6gcc4 6 3 jdk penp 3 sparcSol2 10gcc3 4 2 jdk Solaris Solaris 2 10 No external database support sparc64Sol2 10gcc3 4 2ljdk Executable All Windows platforms listed in the RTI Core Libraries and Utilities Release Windows Notes except those using Visual Studio 2005 2008 on x64 platforms Executabl2. Before 5 0 0 the value of the tag was a boolean indicating whether or not sample synchroniza tion was enabled Starting with version 5 0 0 there are two different kinds of information that can be synchronized independently data samples and durable subscription state The lt synchronization gt tag value is no longer a boolean now it is a complex value that may contain up to three new tags L lt synchronize_data gt L lt synchronize_durable_subscriptions gt I lt durable_subscription_synchronization_period gt Any existing XML configuration files that use the old lt synchronization gt tag as follows lt dds gt lt persistence services lt eynchroni zation gt true lt synchronization gt lt persistence_service gt must be changed to lt dds gt lt persistence_service gt lt synchronization gt lt synchronize data gt true lt synchronize data gt lt synchronization gt lt persistence_service gt For additional information on Persistence Service synchronization see the RTI Persistence Service chapters in the RTI Core Libraries and Utilities User s Manual Available Documentation The following documentation is provided with the Persistence Service distribution The paths show where the files are located after Persistence Service has been installed in lt NDDSHOME gt I Installation instructions RTI Persistence Service Installation Guide lt NDDSHOME gt doc pdf RTI_Persistence_Service_Installa
3. 5 6 5 7 RTI Issue ID PERSISTENCE 62 Error Parsing XML Configuration File with lt use_wait_set gt Tag If the XML configuration file included the tag lt use_wait_set gt Persistence Service failed with error messages such as these RTIXMLParser_onStartTag Parse error at line 658 Unexpected tag use wait set RTIXMLParser parseFromFile Parse error in file lib x64Darwinl0gcc4 2 1 resource xml PsTest xml DDS_XMLParser_parse_from_file Error parsing file PERSISTENCECf gFileManager_ loadCfgFile error parsing XML file PERSISTENCECfgFileManager initialize load configuration file PERSISTENCEC gFileManager new init configuration file manager PERSISTENCEService _initialize init configuration file manager PERSISTENCEService new init persistence service This problem has been resolved RTI Issue ID PERSISTENCE 63 wait_for_historical_data Timed Out when used in Persistent DataReader with direct_communication FALSE If an application called wait_for_historical_data on a DataReader configured with PERSIS TENT or TRANSIENT Durability and durability direct_communication set to FALSE the oper ation may have returned the error code DDS_RETCODE_TIMEOUT even if all the historical data had been received from Persistence Service before the operation timeout expired RTI Issue ID PERSISTENCE 66 Persistent DataReader with direct_communication FALSE Received Samples from Original DataWriter A DataReader configu
4. 1 0 Samples Unexpectedly Removed from Durable Writer History after Restore Operation If a DataWriter using Durable Writer History was restarted after a graceful or ungraceful shut down the samples in the DataWriter s history were removed unexpectedly if the following con ditions were met The DataWriter was configured with a finite lifespan L The DataWriter s property dds data_writer history odbc_plugin in_memory_state was set to zero This issue affected both DataWriters using Durable Writer History and RTI Persistence Service RTI Issue ID CORE 5752 Misleading Error Message if Storage Directory not Found Persistence Service requires that the directory specified with the lt directory gt tag under lt persistence_storage gt must exist If the directory does not exist Persistence Service prints an error message In previous releases the error messages were misleading PERSISTENCEDatabaseManager new init database manager PERSISTENCEService_initialize init database manager PERSISTENCEService new init persistence service main create persistence service This problem has been resolved this release prints the following messages PERSISTENCEDatabaseManager_ initialize storage directory tmp ps does not exist PERSISTENCEDatabaseManager_new init database manager PERSISTENCEService_initialize init database manager PERSISTENCEService new init persistence service What s Fixed in 5 1 0 5 3 5 4 5 5
5. DUR1 The second DataReader should not receive the samples because they were received by the first DataReader on the same Durable Subscription However in previous releases that was not the case This problem has been resolved Notice that even after fixing this issue there are still some conditions under which duplicate samples may be received For example in the scenario described above the second DataReader may receive a duplicate if the first DataReader crashes or is stopped ungracefully before the Per sistence Service DataWriter receives the sample acknowledgments RTI Issue ID PERSISTENCE 79 What s Fixed in 5 1 0 5 9 5 10 5 11 5 12 Out of memory errors when Persisting Keyed Topics and using File Storage on AIX Platforms Running Persistence Service on an AIX platform using file storage and persisting keyed topics could have produced the following error error S1000 1 SQLite out of memory The error was fatal and non recoverable This problem has been resolved RTI Issue ID PERSISTENCE 80 Out of memory Errors when using Durable Subscriptions and File Storage on AIX Platforms Running Persistence Service on an AIX platform using file storage and having durable subscrip tions enabled the default case could have produced the following error after new durable sub scriptions were created error S1000 1 SQLite out of memory The error was fatal and non recoverable This problem has been r
6. lt value gt lt element gt lt element gt lt name gt rti monitor config qos_ library lt name gt lt value gt MyMonitoringQosLibrary lt value gt lt element gt lt element gt lt name gt rti monitor config qos_ profile lt name gt lt value gt MyMonitoringQosProfile lt value gt lt element gt lt value gt lt property gt lt participant_qos gt Persistence Service failed to load the profile MyMonitoringQosLibrary MyMonitoringQosPro file for example from the file USER_QOS_PROFILES xml in the current directory This problem has been resolved and the above configuration will work in any of the Persistence Service participants as long as the specified QoS profile exists in one of the standard QoS config uration files such as USER_QOS_PROFILES xml RTI Issue ID PERSISTENCE 78 Unexpected Duplicate Samples Received by DataReaders Associated with Durable Subscription In previous releases a DataReader that is member of a durable subscription with quorum n may have received a sample even if that sample was already received and acknowledged by n differ ent DataReader members of the same durable subscription For example consider the following scenario 1 Start a DataWriter 2 Start Persistence Service 3 Create a Durable Subscription with name DURI and quorum 1 4 Publish same samples 5 Start a DataReader for DUR1 that receives previous samples 6 Stop the DataReader and start a new DataReader for
7. RTI Persistence Service Release Notes Version 5 1 0 t i 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 RTI DataBus 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 No part of this publication may be reproduced stored in a retrieval system or transmitted in any form including electronic mechanical photocopy and facsimile without the prior written permission of Real Time Innovations Inc The software described in this document 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 support rti com Website https support rti com Release Notes 1 Supported Platforms RTI Persistence Service is included with RTI Connext DDS Professional If you choose to use it it must be installed on top of RTI Connext formerly RTI Data Distribution Service with the same version number Persistence Service is supported on the architectures listed in Table 1 1 Table 1 1 Supported Architectures
8. e No external database support on Windows 8 and Windows Server 2012 R2 2 2 1 2 2 2 3 2 4 Compatibility Persistence Service is compatible with Connext as well as RTI Data Distribution Service 4 5 b e 4 4d 4 3e and 4 2e except as noted below LL Persistence 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 Connext DDS Core Libraries Release Notes d In Connext 5 1 0 the default message_size_max for the UDPv4 UDPv6 TCP Secure WAN and shared memory transports changed to provide better out of the box perfor mance Persistence Service 5 1 0 also uses the new value for message_size_max Conse quently Persistence 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 The types of the remote administration 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 administration are not compatible with Recording Service 5 1 0 e The 5 1 0 Record and Replay shell
9. esolved RTI Issue ID PERSISTENCE 81 Indicator variable required but not supplied Error when using Durable Subscriptions or Application Acknowledgment and MySQL as External Database When using durable subscriptions or application level acknowledgment with Persistence Service you may have seen an Indicator variable required but not supplied error This error only occurred with MySQL as the external database fetch virtual writer info ODBC error 22002 0 unixODBC MySQL ODBC 5 1 Driver mysqld 5 1 44 community Indicator variable required but not supplied This problem has been resolved RTI Issue ID PERSISTENCE 82 Data only Persisted for First Participant Other Participants Ignored Persistence Service only persisted data for the first participant declared in the XML configuration Any additional participants in the XML configuration were ignored For example when using the following configuration Persistence Service did not persist data for DataWriters in domain 57 because the second participant was ignored lt persistence service name MultipleParticipantService gt lt participant name Participant1 gt lt domain_id gt 56 lt domain_id gt lt persistence_group name Group1 gt lt filter gt lt filter gt lt persistence_group gt lt participant gt lt participant name Participant2 gt lt domain_id gt 57 lt domain_id gt lt persistence_group name Group1 gt lt filter gt lt filter gt
10. lt persistence_group gt lt participant gt lt persistence_service gt 6 2 6 3 This problem has been resolved RTI Issue ID PERSISTENCE 84 Known Issues TCP Transport not Supported Persistence Service does not support the TCP transport Coherent Changes not Propagated as Coherent Set Persistence Service will propagate the samples inside a coherent change However it will propa gate these samples individually not as a coherent set BLOBs not Supported by OBDC Storage The ODBC storage does not support BLOBs The maximum size for a serialized sample is 65535 bytes in MySQL
11. red with TRANSIENT or PERSISTENT Durability and durabil ity direct_communication set to FALSE received samples from a TRANSIENT or PERSISTENT DataWriter instead of receiving the samples only from the Persistence Service DataWriters Notice that this issue affected the bandwidth utilization but not application correctness because the DataReader discarded duplicate samples before providing them to the application RTI Issue ID PERSISTENCE 67 Parser Did not Fail when lt administration gt was Missing lt domain_id gt The tag lt domain_id gt within lt administration gt is required but failing to specify it did not gen erate a parsing error This issue did not affect the execution of Persistence Service If lt domain_id gt was not specified the domain ID was set to the default value of 0 This problem has been resolved now if there is no lt domain_id gt within lt administration gt the parser will fail and show an error message RTI Issue ID PERSISTENCE 68 Persistence Service Failed to Enable Monitoring with a Custom QoS Profile When you enable monitoring in a participant you can choose to create it with a different QoS For example lt participant qos gt lt property gt lt value gt lt element gt 5 8 lt name gt rti monitor library lt name gt lt value gt rtimonitoring lt value gt lt element gt lt element gt lt name gt rti monitor config new_participant_domain_id lt name gt lt value gt 54
12. s Admin Console 5 1 0 and Connext 5 1 0 user appli cations performing administration are not compatible with Recording Service 5 0 0 Command Line Options Compatibility Starting with version 4 5b the command line parameter srvName has been replaced with cfgName which is a required parameter Library API Compatibility The following fields in the RTI_PersistenceServiceProperty structure have new names starting in 4 5d Rev 12 L app name has been replaced with application name I stack_size has been replaced with thread_stack_size Persistent Storage When Persistence Service is configured in PERSISTENT mode you may choose between storing the topic data in files or in an external relational database In principle you can use any database that provides an ODBC driver since ODBC is a standard However not all ODBC databases support the same feature set Therefore there is no guarantee that the persistent durability features will work with an arbitrary ODBC driver Persistence Service has been tested with the MySQL 5 1 44 with MySQL ODBC 5 1 6 The usage of MySQL requires the separate installation of the MySQL ODBC 5 1 6 or higher driver For non Windows platforms the installation of UnixODBC 2 2 12 or higher is also required Persistence Service Synchronization Starting with version 5 0 0 the format of the lt synchronization gt tag value under lt persistence_service gt tag has changed Available Documentation
13. tionGuide pdf also avail able for download from the RTI Customer Portal https support rti com L General information on RTI Persistence Service Open lt NDDSHOME gt ReadMe html then select RTI Persistence Service I Example code lt NDDSHOME gt example lt language gt helloWorldPersistence Additional documentation is provided with Connext E Configuration use cases and execution of Persistence Service RTI Connext Core Libraries and Utilities User s Manual lt NDDSHOME gt doc pdf RTI_CoreLibrariesAndUtilities_UsersManual pdf Overview of persistence and durability features Open lt NDDSHOME gt ReadMe html choose your desired API C C or Java then select Modules RTI Connext API Reference Durability and Persistence 4 2 5 2 What s New in 5 1 0 New Platforms This release adds support for the following platforms Ld AIX 7 1 J CentOS and Red Hat Enterprise Linux 6 2 6 4 2 6 kernel L SUSE Linux Enterprise Server 11 SP2 3 x kernel LJ Ubuntu Server 12 04 LTS 2 6 kernel LI Windows 8 32 bit and 64 bit Editions J Windows Server 2012 R2 64 bit Edition Support for Mutable Types This release adds support for mutable types as defined in the Extensible and Dynamic Topic Types for DDS DDS XTypes specification from the Object Management Group OMG Start ing with this release Persistence Service is able to persist topics where the underlying types are mutable What s Fixed in 5
Download Pdf Manuals
Related Search