Liveliness Indication of Writer within the Same Participant doesn't Work as Expected with Automatic Lifetime

[pwueje]

Is there an already existing issue for this?

• I have searched the existing issues

Expected behavior

Instances that are published by a writer with the same participant as the reader should stay alive as long as the writer exists when using the automatic lifetime.

Current behavior

Instances that are published by a writer with the same participant as the reader gets disposed after expiring the lease_duration since the last publish regardless whether the writer is still alive.

Steps to reproduce

1. Create a participant
2. Create a writer and a reader that use the same participant
3. Both are participating on a topic that uses instances
4. Startup reader and writer
5. Publish a message
6. Keep alive writer and reader
7. Wait for lease_duration

Fast DDS version/commit

Fast-DDS 3.2.2

Platform/Architecture

Other. Please specify in Additional context section.

Transport layer

Default configuration, UDPv4 & SHM

Additional context

The issue is not specific to a platform. It could be reproduced on a custom embedded Linux as well on an Ubuntu 24.04.

The transport layer is also not relevant as the behaviour didn't change when switching of Intra-Process.

XML configuration file

Relevant log output

Network traffic capture

No response

[pwueje]

I proposed a fix at PR #6307