Open wangzm-R opened 3 weeks ago
deadlock location;
Hi @wangzm-R, Thank you for using Fast DDS.
In Fast DDS 2.14.1 there are many improvements related to TCP and this issue might be fixed in the latest version. Can you try and let us know if it's fixed?
Is there an already existing issue for this?
Expected behavior
When a subscriber TCP channel is suddenly disconnected, it does not block the normal release data of the publisher;
Current behavior
If a publisher and two subscribers are on unused hardware, and a subscriber's machine suddenly power off, the publisher will be blocked after 1min; once the subscriber's device is activated again, the publisher will return to normal;(use static ip)
Steps to reproduce
use publisher and subscriber;
Fast DDS version/commit
fastdds2.14.0 fastdds2.11.2
Platform/Architecture
Ubuntu Focal 20.04 amd64
Transport layer
TCPv4
Additional context
No response
XML configuration file
No response
Relevant log output
No response
Network traffic capture
No response