-
Notifications
You must be signed in to change notification settings - Fork 791
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect state of Liveliness of Readers who accept data from a single Writer #4610
Comments
The issue arises from the use of the
|
Hi @i-and, |
Hi @i-and and sorry for the late response. |
Hi @Mario-DL |
Is there an already existing issue for this?
Expected behavior
The correctness of the Liveliness of Readers should not depend on their number.
Current behavior
Incorrect state of Liveliness of Readers who accept data from a single Writer
Steps to reproduce
Developed a test based on the HelloWorldExample code in accordance with the attached patch. In the HelloWorldExample on the subscriber's side, another Reader of the existing HelloWorldTopic was simply added.
To repeat this situation, you need to open two terminals and perform the following sequence of actions.
./DDSHelloWorldExample publisher -s 0 -i 2000
./DDSHelloWorldExample subscriber
alive_count=0 not_alive_count=0 alive_count_change=-1 not_alive_count_change=0
./DDSHelloWorldExample publisher -s 0 -i 2000
alive_count=2 not_alive_count=0 alive_count_change=1 not_alive_count_change=0
insteadalive_count=1 not_alive_count=0 alive_count_change=1 not_alive_count_change=0
alive_count=1 not_alive_count=1 alive_count_change=-1 not_alive_count_change=1
insteadalive_count=0 not_alive_count=1 alive_count_change=-1 not_alive_count_change=1
./DDSHelloWorldExample publisher -s 0 -i 2000
alive_count=2 not_alive_count=1 alive_count_change=1 not_alive_count_change=0
insteadalive_count=1 not_alive_count=0 alive_count_change=1 not_alive_count_change=0
Log from terminal 2:
HelloWorld example code patch:
Fast DDS version/commit
2.13.0
Platform/Architecture
Ubuntu Focal 20.04 amd64
Transport layer
Default configuration, UDPv4 & SHM
Additional context
No response
XML configuration file
No response
Relevant log output
No response
Network traffic capture
No response
The text was updated successfully, but these errors were encountered: