Solutions

Note: Applies to RTI Connext 4.1 and above. Use the transport properties for the UDPv4 transport to restrict which interfaces the transport will attempt to use. The properties allow you to either use an "allow" list (to specifically allow certain interfaces), or a "deny" list (to specifically deny ...
3240 reads — 0 comments
Note: Applies to RTI Connext 4.5c and above. This solution applies if you are seeing errors during rtiddsgen code-generation which look like the following (rtiddsgen used with –language java for this example): javax.xml.transform.TransformerException: org.xml.sax.SAXException: /p8core/interface/ ...
4976 reads — 0 comments
Not all API calls are safe. In general, the get / set_default_XXX_qos() and lookup_xxx() APIs are not thread-safe. The online HTML documentation for various API calls commonly include one or more MT Safety sections which describe any concerns about the use of individual calls in multi-threaded ...
2882 reads — 0 comments
Note: Applies to RTI Connext 4.4c and higher. By default, rtiddsgen uses JRE 1.4, which is distributed with RTI Connext in $NDDSHOME/jre . If you can not use JRE 1.4 on your computer, the following instructions can help you run rtiddsgen with a Java 5 or Java 6 JRE. To use rtiddsgen with Java 1.6, ...
2062 reads — 0 comments
One potential cause of poor performance on a Linux system is the amount of buffer space the RHEL 4u4 kernel uses to reassemble IP fragments. The parameters in /proc/sys/net/ipv4 control various aspects of the network, including a parameter that controlls the reassembly buffer size. ...
8977 reads — 0 comments
Note: Applies to RTI Connext 4.x and above RTI Connext does not support the IDL interface data type because it corresponds to remote procedure calls, a concept that does not apply to the data-centric, publish-subscribe (DCPS) communications model of the DDS standard. The valuetype data type is ...
3736 reads — 0 comments
Note: Applies to RTI Connext 4.x and above and Red Hat Enterprise Linux 5. If DDS_DomainParticipantFactory_set_qos() crashes, the stack trace begins with free () from /lib/libc.so.6 and if you're making any calls to mlockall() , explicitly or implicitly, you may be running into a known bug in glibc ...
1798 reads — 0 comments

Pages