imhappy

@JesusPoderoso [Tested ](https://github.com/chunyisong/test-dds/tree/main)with [fastdds 2.14.1](https://github.com/eProsima/Fast-DDS/tree/v2.14.1) today, and deadlock easily appeared. I tested on localhost with discovery server follows: 1. Start discover server in a console : bin/fast-discovery-server -i 0 -t...

@JesusPoderoso According to document of [max_blocking_time](https://fast-dds.docs.eprosima.com/en/v2.14.1/fastdds/dds_layer/publisher/dataWriter/publishingData.html#blocking-of-the-write-operation),writer should return with timeout. But in fact,writers will always get stucked with the deadlock, and will never return.So, this situation is not in line...

>  > > the deadlock stack； > > use 2.11.2, if deadlock occurs, it cannot recover, but use 2.14.0, if a deadlock occurs, then recreate the subscriber， deadlock will...

Today I test fastdds v2.14.2 with one publisher connected to two subscribers,using 2000 topics, and the deadlock almost always appeared.Also test built-in LARGE-DATA mode and custom larg-data.All attempts have shown...