Release Notes - Community RTI Connext Users
Contents
1. Supported Platforms RTI Routing Service is supported on these platforms Supported Platforms Platform Operating System Architecture INTEGRITY INTEGRITY 10 0 2 pentiumInty10 0 2 pcx86 i86Linux2 6gcc4 1 2 CentOS 5 4 5 5 2 6 kernel vedliu geia i86Linux2 6gcc4 4 5 eas tats sane x64Linux2 6gcc4 4 5 Raspbian Wheezy 7 0 armv6vfphLinux3 xgcc4 7 2 i86Linux2 6gcc4 1 1 Linux ees x64Linux2 6gcc4 1 1 i86Linux2 6gcc4 1 2 Red Hat Enterprise Linux 5 1 5 2 5 4 5 5 x64Linwx2 6g c4 1 2 i86Linux2 6 cc4 4 5 Red Hat Enterprise Linux 6 0 6 4 i TR a x64Linux2 6gcc4 4 5 i86Linux3 xgcc4 6 3 Ubuntu Server 12 04 LTS 2 6 kernel GALS reci 63 i86Win32VS2005 sae aa 4 i86Win32VS2008 Windows Server 2008 R2 eee i86Win32VS2012 Windows Windows Server 2012 R2 x64Win64VS2005 Windows 2003 Wind Vista x64Win64VS2008 sa ped ed PR N x64Win64VS2010 ee graces ne x64Win64VS2012 1 Does not include TCP IPv4 transport plugin implemented as a static library Routing Service is also supported on the platforms listed in Table 1 1 these are target platforms for which RTI offers custom support If you are interested in these platforms please contact your local RTI representative or email sales rti com Supported Languages Table 1 1 3 1 1 Custom Supported Platforms Operating System CPU Compiler RTI Architecture Abbreviation NI Linux ARMv7 gcc 4 4 1 armv7Angs2. L Release Notes RTI_Routing Service_ReleaseNotes pdf Describes system require ments and compatibility as well as any version specific changes and known issues 11 Available Documentation L Getting Started Guide RTI_Routing_Service_GettingStarted pdf Highlights the bene fits of Routing Service It provides installation and startup instructions and walks you through several examples so you can quickly see the benefits of using Routing Service L Users Manual RTI_Routing Service_UsersManual pdf Describes how to configure Routing Service and use it remotely
3. lt value gt lt property gt lt transformation gt 3 4 Transformation API The transformation API of Routing Service 2 0 1 and higher is not compatible with the API of pre vious releases 2 0 0 and lower The new API follows the same model as the adapter API which introduced the concept of a Plu gin as a C structure that contains all the function pointers that implement the interface The registration of a transformation plugin with the new model requires a single entry point to the shared library the entry point is a function that creates the Plugin structure which contains the implementation For example lt transformation library name MyTransfLib gt lt transformation plugin name MyTransfPlugin gt lt dllsmytransformation lt dll gt lt create_function gt lt Entry point gt MyTransfPlugin_ create lt create_function gt lt transformation_plugin gt lt transformation_library gt The following table shows how deprecated functions map to the new API Compatibility 2 0 0 API rti_routingservice h 2 0 1 and Higher API routingservice_transformation h Comments RTITransformationClass_ loadFnc RTI_RoutingServiceTransformation Plugin_CreateFcn This is the entry point function RTITransformationClass_ unloadFnc Function declaration RTI_RoutingServiceTransformation Plugin_DeleteFcn Member in Plugin struct transformation_plugin_delete RTITransforma
4. name gt lt participant_name gt Routing Service will use the default name as described above RTI Routing Service MySer vice MyDomainRoute 1 The DomainParticipants created for remote administration and monitoring will also honor user specified names What s Fixed in 5 1 0 5 2 5 3 5 4 5 5 5 6 5 7 What s Fixed in 5 1 0 Possible Crash During Transformation if Monitoring Enabled Routing Service may have crashed while gathering statistics for samples that go through a trans formation This problem only occurred if monitoring was enabled and a transformation plug in released a sample in its return_loan function RTI Issue ID ROUTING 139 Possible Segmentation Fault upon Discovery of Types with Bit Fields If Routing Service discovered a DataReader or DataWriter whose type contained bit fields it may have issued a segmentation fault Routing Service does not support bit fields see Section 6 4 but now it will handle the error appropriately RTI Issue ID ROUTING 162 Possible Crash when Updating Any Routing Service Entity with Invalid Configuration when Disabled Routing Service may have crashed if an update operation of any entity was performed on a dis abled service If the updating configuration provoked an error a crash may have occurred while retrieving the remote administration logger used to report the update error This problem has been resolved RTI Issue ID ROUTING 171 Possible Cr
5. Command Line Options Compatibility Starting with Routing Service 1 1 0 the command line parameter srvName has been replaced with cfgName to select a configuration and appName to name the service execution In pre vious Routing Service versions the srvName parameter was not required However in this ver sion the equivalent parameter cfgName is required Also starting with Routing Service 1 1 0 the allowed values for the verbosity command line option changed The new verbosity option coalesces the old verbosity and ddsVerbosity options into a single parameter For additional information about command line options see Chapter 3 in the Routing Service Getting Started Guide XML Compatibility l Starting with Routing Service 1 1 0 the attribute name in the lt routing_service gt tag is now required Old XML files without the name attribute will not be parsed by Routing Service 1 1 0 and higher LI Starting with Routing Service 2 0 0 the way to register and configure transformations in the configuration file has changed e The tag lt transformation_class_library gt has been replaced with lt transformation_library gt e The tag lt transformation_class gt has been replaced with lt transformation_plugin gt e The content of these tags has also changed With the new configuration there is only a single entry point to the library For example lt transformation library name MyTransfLib gt lt transformati
6. R2 Filter Propagation This release enables support for propagation of the filter information from DataReaders using a ContentFilteredTopic This feature can be enabled by using the tag lt filter_propagation gt within lt topic_route gt See Section 2 4 6 and Chapter 9 in the RTI Routing Service User s Manual Ability to Override Name of Participants Created by Routing Service When Routing Service creates a DomainParticipant it uses a specific format for its name which gets propagated on the wire RTI Routing Service service name domain route name 1 2 where service name domain route name are the names of the service and domain route that contain that participant followed by 1 or 2 indicating if it is the first or second participant in that domain route In previous releases it was not possible to change this name Now when specified Routing Ser vice will use the name specified through the DomainParticipant QoS For example when using the following configuration Routing Service will create a participant named MyParticipant lt routing service name MyService gt lt domain_route name MyDomainRoute gt lt participant_1 gt lt participant_qos gt lt participant name gt lt name gt MyParticipant lt name gt lt participant_ name gt lt participant_qos gt lt participant_1 gt lt domain_route gt lt routing service gt If you omit the line lt participant_name gt lt name gt MyParticipant lt
7. RTI Routing Service Release Notes Version 5 1 0 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 RTI 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 Contents 1 Supported Platforms cccssssssssscsssssessssscssssssssseseseessssesessecssssssseseesesssssseseesesesseseeseseseessesessseessseseseeneneees 1 2 Supported Languages cceccrcecececsersessecesssssssesesesesssssesesssssssssesesesssssssssesessesssseseseseesssseecsesseseseseeeeesenes 2 3 Compatibility occ eesessssesecesessscsesesesssesssssesesesssssesesesssssssesesssnsssnsesesesnsssesesesssasssesensasssese
8. a Reported when Statistics Sampling Period Equal or Longer than Publication Period sisisi rissies iessen tients caine riaa aka aaea aeaa aaan Eaa Ei 9 iii 5 18 Routing Service did not notify StreamWriters of Disposed or Unregistered DDS AStA NCES h isi faiths ides abit ssi destalssirvase a Mit hastens mata nae ash ates 5 19 Parser did not Report Error if lt domain_id gt not in lt administration gt Tag cceee 5 20 Minor Errors in Default Configuration File RTILROUTING_SERVICE xml ce 5 21 Inconsistent QoS Settings for Remote Administration and Monitoring Entities if Loaded QoS Profile was Marked is_default_QOS true c ccccscseecesesceesssesteneeseseeneesesnenenens 6 KOWN ISSUES scsscssssssssesesressssesscsensnsessnsenenssnssssnsssensssssseseasesenseseaseseaseseaseseaseseaseneaseneaseneasenssseasssseesenees 6 1 Limitationssini Adapter API as e seuss loves nteconee E E e p EE ERER 6 2 Sequences of Transformations in a Route not Supported ss ssssesstsrtssstertttsttertesstrsrtessses tes 6 3 Assignment Data Transformation only Supports Assignment of Primitive Fields hot Part of Arrays Or Sequences sami pipoa ata a ra a raaa E 6 4 Topics of Data Types with Bit Fields are not Supported ccceeccescceesesesteneeseecesesesesnenenens 7 Available Documentation ccecececsssrseececessssessecscessessssesecesssssesessssessssesesessessssesesesssssssesessssseseseseeeeees Release Notes Table 1 0
9. ash after Updating Disabled DomainRoute Updating a disabled Domain Route for example to change an immutable DomainParticipant QoS policy may have caused Routing Service to crash This problem has been resolved RTI Issue ID ROUTING 190 Routing Service Entered Infinite Loop upon XML DTD Validation Error During Start Up If an XML DTD validation error occurred while Routing Service was starting it may have hung in an infinite loop due to finalization cleanup This problem has been resolved RTI Issue ID ROUTING 192 Deserialization Errors when Using Topic Route if Input Type Contained Unions or Sequence Members Routing Service may have produced deserialization errors upon sample reception if the service configuration contained a topic route where the input type contained members whose types were sequences or unions This issue has been resolved RTI Issue ID ROUTING 150 Deserialization Errors if Topic Route s Input Type was a Valuetype Routing Service may have produced deserialization errors like the one below if the service con figuration contained a topic route in which the input type was a valuetype DDS_DynamicData_from_stream ERROR Failed to get sample serialized size This issue has been resolved RTI Issue ID ROUTING 153 What s Fixed in 5 1 0 5 8 5 9 5 10 5 11 Remote Update Failed when Sending Well Formed Service Configuration with Default Name If a well formed string configuration was sent
10. easasssssseesesssenes 2 3 1 Connext Compatibility c c scecccesscccecrsastvencasentasnseosesneronnasenducnsrssessseoncssedshensastadssgetsenedetsvesesestepeesesea 2 3 2 Command Line Options Compatibility ccccccecsesesteeececeeesescsnensnesesesneesescecenesesssneeneneeeeees 3 3 3 XME Compatibility eseese esaeen repis erei EIEE ENEE EEEE aaelessetasectes abscesteaguscesctenis 3 3 4 Transformaton A Plisseren E AE R ASE EE EE T E E EE 4 4 Whats New in 5 1 0 wo cesssssscsesssssssesssssssnssssscssesssensessssssssessessssesssssseesesssssssesesaessssssesseassssseesseeasasssseeeeeaenees 6 4 1 New Platforms saisang nnie niaii a nais ain testa css saab oaa E Oir aasa PAE an SRE EER 6 4 2 Filtet Propa ation sssiccs isiin sadean state eassitvis eeeistan anette 6 4 3 Ability to Override Name of Participants Created by Routing Service ss sssssessssesseseeese 6 5 Whats Fixed if 5A Onscreen Are EE E R RERS 7 5 1 Possible Crash During Transformation if Monitoring Enabled c cccccseseseteeeteteseeeeeenes 7 5 2 Possible Segmentation Fault upon Discovery of Types with Bit Fields 00 0 0 cece 7 5 3 Possible Crash when Updating Any Routing Service Entity with Invalid Configuration when Disabled c ccccccccssssesssteescecesescsescensneseseecesescececesesesesesnensieseeceeessessnanenes 7 5 4 Possible Crash after Updating Disabled Domain Route cccccccccecceseeesteneteteseeteneseeeeeenes 7 5 5 Routing Service Entered Infinite Loop upo
11. in a command to update Routing Service and that configuration had the same name as any of the default ones the operation would fail with a parser error This issue was noticeable when using RTI Admin Console to modify the service con figuration when it was loaded with a default one This issue has been resolved now when this situation happens the updating configuration will override the default one with the same name RTI Issue ID ROUTING 169 Incorrect Handling of Samples if Received Type was Valuetype Marked as Extensible Routing Service did not correctly handle samples if the received type was a valuetype marked as extensible The following error was reported DDS_DynamicData_from_stream ERROR Failed to get sample serialized size This only happened when the valuetype was marked as extensible and it was the top level type This problem has been resolved RTI Issue ID ROUTING 149 When Saving XML Configuration New Filter Level not Saved if Modified Remotely When saving Routing Service s XML configuration the Distributed Logger configuration was saved but if the filter level had been modified this was not reflected in the saved XML configu ration Instead the initial parsed value was used RTI Issue ID DISTLOG 19 XML Save Functionality did not Replace Predefined Entities by Their Names If the Routing Service XML configuration contained an XML predefined entity name such as amp lt or amp gt inside a lt content_fi
12. isposed unregistered samples and there is no tag to enable that This problem has been resolved Now Routing Service will always propagate dispose unregister samples in the previous situation so that StreamWriters can get notified when a DDS instance has been disposed or unregistered RTI Issue ID ROUTING 215 Parser did not Report Error if lt domain_id gt not in lt administration gt Tag The tag lt domain_id gt is required within lt administration gt according to the documentation and the XSD but failing to specify it did not generate a parsing error in the previous release This issue did not affect the execution of Routing 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 if the lt domain_id gt tag is not found within lt administration gt the parser will fail and report an error message RTI Issue ID ROUTING 86 Minor Errors in Default Configuration File RTL ROUTING_SERVICE xml The default configuration file RTILROUTING_SERVICE xml1 included some incorrect filters These filters should have prevented Routing Service from creating topic routes for RTI Distributed Logger Topics As a consequence in some cases Routing Service created superfluous topic routes for Distributed Logger topics This problem has been resolved now Routing Service will exclude the correct topics RTI Issue ID ROUTING 137 Inconsistent QoS Settings for Remote Ad
13. lter gt tag and a request was sent to Routing Service to either 1 save the configuration to a file or 2 view the configuration in RTI Admin Console instead of saving sending the XML as read Routing Service converted the predefined entity name to the corresponding predefined entity character such as lt or gt This led to invalid XML syntax that could not be reloaded by Routing Service or viewed in Admin Console For example suppose you had the following valid XML lt content_filter gt lt expression gt value amp gt 100 OR value amp lt 32 lt expression gt lt content_filter gt This would have been converted to the following invalid XML before being saved to a file or sent to Admin Console lt content_filter gt lt expression gt value gt 100 OR value lt 32 lt expression gt lt content_filter gt This problem has been resolved RTI Issue ID ROUTING 189 What s Fixed in 5 1 0 5 12 5 13 5 14 5 15 5 16 5 17 Failure to Close Files with XML Snippet used to Update Routing Service Any file containing an XML snippet that was used to update Routing Service was not closed after the update operation causing a memory leak This problem has been resolved RTI Issue ID ROUTING 212 Get Key Value Error and Failure to Propagate Dispose Message for Sample in Some Cases If Routing Service was configured to propagate dispose messages and the dispose message was the first message e
14. ministration and Monitoring Entities if Loaded QoS Profile was Marked is_default_qos true If there was a QoS profile marked is_default_qos true in the USER_QOS_PROFILES xml file Routing Service would use this profile to create the DDS entities for remote administration and monitoring This behavior resulted in inconsistent profiles because Routing Service would overwrite some default QoS values for the administration and monitoring entities In this release Routing Service will ignore any profile marked as is_default_qos true You can still specify a profile in USER_QOS_PROFILES xml For example the following con figuration allows you to use a DataWriter QoS profile named MyProfile in the QoS library MyLibrary for the remote administration DataWriter lt routing service name MyRoutingService gt lt administration gt lt datawriter gos base name MyLibrary MyProfile gt lt administration gt lt routing service gt RTI Issue ID ROUTING 114 Known Issues 6 2 6 3 6 4 Known Issues Limitations in Adapter API In the Adapter API Connection get_attributes and update operations are currently not sup ported RTI Issue ID ROUTING 222 Sequences of Transformations in a Route not Supported The tag lt transformation_sequence gt within a lt topic_route gt is not supported Only one transfor mation per route is supported RTI Issue IDROUTING 223 Assignment Data Transformation only S
15. n XML DTD Validation Error During Start UPa e tases se o E Eusa aeaaee EEEE EE EEE E E e TE tine EEE EEEE EE 7 5 6 Deserialization Errors when Using Topic Route if Input Type Contained Unions or Sequence Member Sussy sanee aa i prensa esaia AALER anai RES Eaei 7 5 7 Deserialization Errors if Topic Route s Input Type was a Valuetype cscsccecseseeeseeneneens 7 5 8 Remote Update Failed when Sending Well Formed Service Configuration with Default ET a asc E E cscs avs ohne cafe castes ccatetsc eid ses tast Sis cebtycsi th de sbas sess vesepagvstatassesacouie thts 8 5 9 Incorrect Handling of Samples if Received Type was Valuetype Marked as Extensible 8 5 10 When Saving XML Configuration New Filter Level not Saved if Modified Remotely 8 5 11 XML Save Functionality did not Replace Predefined Entities by Their Names 8 5 12 Failure to Close Files with XML Snippet used to Update Routing Service cccecee 9 5 13 Get Key Value Error and Failure to Propagate Dispose Message for Sample in Some CASES E E E E E EEE 9 5 14 Delay in Publishing Entity Data Topic for Routes Created from Auto Routes 9 5 15 Host Free Swap Memory and Total Swap Memory Reported as Zero Windows Systems Only cissicntiedssnscscecsssasessseeasusvees sscsesnssslustecssedsiaedsbasaciste ssneasdsbatads shsenveen tees 9 5 16 Failure to Enable Remote Administration when Loading Java 7 Adapters ccccccee 9 5 17 Incorrect Monitoring Dat
16. nsole 5 0 0 and RTI Connext 5 0 0 user applications performing monitoring administration are not compatible with RTI Routing Service 5 1 0 The 5 1 0 RTI Routing Service shell RTI Admin Console 5 1 0 and RTI Connext 5 1 0 user applications performing monitoring administration are not compatible with RTI Routing Service 5 0 0 RTI Data Distribution Service 4 2e Compatibility If the applications data types contain 8 byte or larger primitive types double long long unsigned long long or long double Routing Service will have to be run with the command line option use42eAlignment in order to be compatible with RTI Data Distribution Service 4 2e If the applications use large data Routing Service must be configured with the following proper ties set to 1 in order to be compatible with RTI Data Distribution Service 4 2e 1 See lt Connext installation directory gt ndds lt version gt doc pdf RTI_CoreLibrariesAndUtilities_ReleaseNotes pdf Compatibility 3 2 3 3 L dds data_writer protocol use_43_large_data_format L dds data_reader protocol use_43_large_data_format RTI Data Distribution Service 4 3e Compatibility If the applications use large data Routing Service must be configured with the following proper ties set to 1 in order to be compatible with RTI Data Distribution Service 4 3e L dds data_writer protocol use_43_large_data_format L dds data_reader protocol use_43_large_data_format
17. on plugin name MyTransfPlugin gt lt dll gt mytransformation lt dll gt lt create_function gt lt Entry point gt MyTransfPlugin create lt create_function gt lt transformation_plugin gt lt transformation_library gt e The configuration of a transformation within lt route gt is done using properties instead of the lt expression gt and lt parameter gt tags For example lt transformation plugin _name TransformationLib Assignment gt lt property gt lt value gt lt element gt lt name gt X lt name gt lt value gt Y lt value gt lt element gt Compatibility lt element gt lt name gt Y lt name gt lt value gt X lt value gt lt element gt lt value gt lt property gt lt transformation gt e The configuration of the assignment transformation distributed with Routing Ser vice is now done with properties For example Before 2 0 0 lt transformation className TransformationLib Assignment gt lt expression gt lt expression gt lt parameter gt position x position y lt parameter gt lt parameter gt x 10 lt parameter gt lt transformation gt In 2 0 0 and higher lt transformation plugin _name TransformationLib Assignment gt lt property gt lt value gt lt element gt lt name gt position x lt name gt lt value gt position y lt name gt lt element gt lt element gt lt name gt x lt name gt lt value gt 10 lt name gt lt element gt
18. tach native thread to JVM After reporting this error Routing Service failed to enable remote administration but would con tinue to run This problem has been resolved RTI Issue ID ROUTING 170 Incorrect Monitoring Data Reported when Statistics Sampling Period Equal or Longer than Publication Period Applications subscribing to Routing Service s monitoring topics may have received status sam ples in which some fields had a value of zero This happened periodically some samples were correct some were not when statistics_sampling period was equal or larger than status_publication_period This problem has been resolved Now when statistics_sample_period is longer than the status_publication_period Routing Service may publish the exact same statistics two or more times in a row until Routing Service re samples the statistics RTI Issue ID ROUTING 203 What s Fixed in 5 1 0 5 18 5 19 5 20 5 21 Routing Service did not notify StreamWriters of Disposed or Unregistered DDS Instances When a DDS input receives a NOT_ALIVE_DISPOSE or NOT_ALIVE_NO_WRITERS message it can propagate it to the route s transformation if any and the output You can configure this behavior when defining a lt topic_route gt by using the tag lt propagate_dispose gt or lt propagate_unregister gt However when you use a lt route gt with a lt dds_input gt and an adapter based non DDS lt out put gt Routing Service did not propagate d
19. tionClass_ createFnc RTITransformationClass_ deleteFnc Function declaration RTI_RoutingServiceTransformation Plugin_CreateTransformationFcn Member in Plugin struct transformation_plugin_create_ transformation Function declaration RTI_RoutingServiceTransformation Plugin_DeleteTransformationFcn Member in Plugin struct transformation_plugin_delete_ transformation RTITransformationClass_ modifyFnc Function declaration RTI_RoutingServiceTransformation_ UpdateFcn Member in Plugin struct transformation_update RTITransformationClass_ Function declaration RTI_RoutingServiceTransformation_ TransformFcn In the new API the transform function accept multiple samples In addition the output samples transformFnc f i must be created by the Member in Plugin struct f g f transformation instead of being transformation_transform passed in by Routing Service Function declaration RTI_RoutingServiceTransformation_ This function is used to return the none ReturnLoanFen loan on the samples returned by Member in Plugin structure transformation_return_loan the transform function What s New in 5 1 0 4 2 4 3 What s New in 5 1 0 New Platforms This release adds support for the following platforms L CentOS 6 2 6 4 L Raspbian Wheezy 7 0 L Red Hat Enterprise Linux 6 2 6 4 J Ubuntu Server 12 04 LTS 2 6 kernel L Windows 8 L Windows Server 2012
20. tromLinux3 2gcc4 4 1 cortex a9 Supported Languages L The transformation plugin API is only available in C L The adapter plugin API is available in C and Java Compatibility Connext Compatibility Routing Service can be used to forward and transform data between applications built with RTI Connext as well as RTI Data Distribution Service 4 5 b e 4 4d 4 3e and 4 2e except as noted below LI Routing Service is not compatible with applications built with RTI Data Distribution Service 4 5e and earlier releases when communicating over shared memory For more informa tion please see the Transport Compatibility section in the RTI Core Libraries and Utilities Release Notes LJ 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 Routing Service 5 1 0 also uses the new value for message_size_max Conse quently Routing 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 and monitoring topics in 5 1 0 are not compatible with 5 0 0 Therefore The 5 0 0 RTI Routing Service shell RTI Admin Co
21. upports Assignment of Primitive Fields not Part of Arrays or Sequences The data transformation library distributed with Routing Service only supports the assignment of primitive fields including strings that are not part of arrays or sequences For example lt transformation className TestTransformationLib FieldMapping gt lt expression gt lt expression gt lt parameter gt position x position y lt parameter gt lt This is supported gt lt parameter gt x y lt parameter gt lt This is supported gt lt parameter gt x 0 y 0 lt parameters gt lt This is not supported gt lt parameter gt position position lt parameter gt lt This is not supported gt lt transformation gt For additional details about data transformation see Chapter 3 in the Routing Service User s Man ual RTI Issue IDROUTING 224 Topics of Data Types with Bit Fields are not Supported Routing Service cannot communicate with DataReaders or DataWriters of Topics with a data type that includes bit fields You may see the following messages but Routing Service will continue to work normally otherwise DDS DynamicDataTypeSupport_initialize type not supported bitfield member ROUTERTypeInfo_initialize create dynamic data type support ROUTERTypeInfo new init ROUTERTypeInfo object ROUTERDdsConnection_assertType create type info RTI Issue ID CORE 3949 Available Documentation Routing Service documentation includes
22. ver received from a specific instance Routing Service did not propagate the dispose message You may have seen a get key value error This problem has been resolved RTI Issue ID ROUTING 133 Delay in Publishing Entity Data Topic for Routes Created from Auto Routes In some cases Routing Service waited for certain events to occur before it would publish an entity data topic that described the routes created from an auto route These events included the creation of the route s input or output or receipt of a command that changed the route s descrip tion such as a Pause command You may have noticed this behavior in RTI Administration Console For example after sending a Pause command several new routes may have suddenly appeared RTI Issue ID ROUTING 138 Host Free Swap Memory and Total Swap Memory Reported as Zero Windows Systems Only When monitoring was enabled host information including free swap memory and total swap memory was reported as zero on Windows platforms This issue has been resolved Now the swap information is sent and computed as virtual memory minus physical memory from the values provided by the Windows API GlobalMemoryStatusEx RTI Issue ID ROUTING 154 Failure to Enable Remote Administration when Loading Java 7 Adapters Users running Routing Service adapters with Java 7 while remote administration was enabled may have seen the following error message ROUTERJUNIGlobal_attachCurrentThread at
Download Pdf Manuals
Related Search