Hi,
I am trying the example "rticonnextdds-examples/examples/connext_dds/using_qos_profiles", and it looks DomainParticipant shutdown ( or release resources) needs about 3 seconds. I did a test with only DomainParticipant as below:
Hi,
I am trying the example "rticonnextdds-examples/examples/connext_dds/using_qos_profiles", and it looks DomainParticipant shutdown ( or release resources) needs about 3 seconds. I did a test with only DomainParticipant as below:
MQTT provides a "Last Will & Testament" QoS, that causes a writer to emit a final instance when it it shuts down, effectively a shut-down hook.
I want to implement the same thing using DDS {in Java*}. I'm looking for different ideas on what might be a best-practice...
I want to avoid writing my own manual shutdown algorithm (I want to call <participant>.delete_contained_entities(), and have that trigger a final sample being published).
At the moment I'm subclassing the data writer: