Connection Lost Functionality issue in docker container

Please fill out the form below before submitting, thank you!

- [ ] Bug exists Release Version 1.2.3 ( Master Branch)
- [x] Bug exists in MQTTv3 Client on Snapshot Version 1.2.4-SNAPSHOT (Develop Branch)
- [ ] Bug exists in MQTTv5 Client on Snapshot Version 1.2.3-SNAPSHOT (Develop Branch)

If this is a bug regarding the Android Service, please raise the bug here instead: https://github.com/eclipse/paho.mqtt.android/issues/new

Hello,

On a network disconnect, connection loss takes almost 20 minutes to trigger. The environment set up is a centOS system with MQTT running inside a docker container. The only setting applied is clean session turned to true. Auto-Reconnect is in its default state. The same application outside a docker container in a windows environment takes under a minute to detect a connection loss. Why is there such a huge delay for connection loss to trigger?

No files, tests, or entry points are named. Reproduce the network disconnect with the MQTTv3 client on the 1.2.4-SNAPSHOT develop branch in the described CentOS Docker setup, then compare it with the Windows run. Done means identifying the cause of the delay and documenting or testing the expected connection-loss detection behavior.

Written by the indexing model from the issue text.