SHM Subscriber not matching if durability volatile and Domain::stopAll not called [13664]

[aleksas]

Expected Behavior

After critical subscriber process kill and process restart subscriber should successfully pair up with publisher with subscriber participant Rparam.qos.m_durability.kind set to VOLATILE_DURABILITY_QOS.

Current Behavior

If subscriber participant Rparam.qos.m_durability.kind is set to VOLATILE_DURABILITY_QOS and process is killed and Domain::stopAll() not called restarting subscriber fails to pair up with publisher.

Steps to Reproduce

1. In HelloWorldExampleSharedMem remove Domain::stopAll(); line.
2. Change subscriber participant Rparam.qos.m_durability.kind parameter to VOLATILE_DURABILITY_QOS.
3. Change message count and sleep period to 10000 and 2000 respectively
4. Run both publisher and subscriber example instances
5. Kill subscriber instance (e.g. ^C)
6. Run subscriber instance again.

System information

Experiments are ran within docker container sharing shm resources with host os. (docker with --ipc=host parameter)

• Host OS:

  • CentOS Linux release 7.9.2009 (Core)

• Container OS:

  • CentOS Linux release 7.9.2009 (Core)

• Fast-RTPS version:

  • 2.1.x branch
  • commit: c92a75676a2ef2645706eeee309ad6a7c45886f1