Skip to content

Disconnects are not detected #209

@hvanoch

Description

@hvanoch

I am experimenting with library. But simple usecases are not working as expected.

A case that I have is that I connect to the MQTT server and subscribe. That works fine.
If for some reason the connection to the MQTT server breaks, this is never detected.

Example: We use docker, if I for instance kill or stop the MQTT container, my client never detects that the MQTT server is not there anymore. It does still send data over the socket and tries to read from it. But it reads empty data.

This causes the process to just become stuck. Even if I start the MQTT container again, this is not picked up by the client.

I would expect that it has some detection, that if it doesn't receive any data for x time, it will raise an exception somewhere. That would be a trigger point to interrupt and try to connect again.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions