DDS Routing Service

We are planning on having a point-to-point transport between two Router services that will be over a low-bandwidth communication path.  Because of this, we want to disable all of the discovery traffic and as much of the "meta" traffic as possible.  Given this, is there a way to configure reader QoS such that it detects liveliness based solely receipt of instance samples?  Put another way, is there a way to eliminate liveliness assertions and still have liveliness?

What is the recommended way of forwarding liveliness state when using the RTI Routing services?

Suppose we what this scenario:  We have a router configured at Site A to subscribe to a topic, transform it, and publish the transformed version back out on a point-to-point connection to another router at Site B.  The router at Site B simply republishes the topic on the multicast transport.

Language: Java

RTI Version: 5.3.1.22

Hi,

I am launching 3 routing service instances via the RTIRoutingService.bat files which launch rtiroutingservice.exe programs.

Due to the inability to configure the routing service to log directly to a file I am forced to use the RTI Distributed Logger to receive log messages.

I'm trying to run the Routing Service example from the github repo. It compiles just fine, but when I try to run in either of the configurations I get this error: 

Hi,

Hello,

I'm running into some touble while transforming data using the the RTI Router.

Basically, I have a type (let's call it NetworkEntity) which contains a single field (called "entity") of a complex type (let's call it InnerEntity) which contains primitives. The Router seems to have a problem accessing the members of the complex type (InnerEntity).

I used the example transformation library as a template, and the following code is taken from the createOutputSample method (I removed the error checking blocks for convenience):