Handling liveliness with RTI Routing Services

3 posts / 0 new
Last post
Offline
Last seen: 1 year 8 months ago
Joined: 02/07/2020
Posts: 12
Handling liveliness with RTI Routing Services

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.

Given this, suppose the Site A router goes down (or the communications are severed).  At some point, Site B's subscription to Site A will detect liveliness lost.  How do we then cause Site B to stop asserting liveliness for the republished topic?

Offline
Last seen: 2 years 1 month ago
Joined: 08/20/2012
Posts: 25

Have you tried it, and it's not working? The default for <propagate_unregister> and <propagate_dispose> is 'true'. Is the transformation maybe not cooperating, as suggested in those docs?

 

Offline
Last seen: 1 year 8 months ago
Joined: 02/07/2020
Posts: 12

No, I haven't tried it yet.  The router is new to us, and we are just started working with the service APIs.  I had not spotted those settings in the configuration.  Thank you for pointing them out.