Timeout ignored when TLS is active

[wolfssl]

Timeout ignored when TLS is active

[embhorn]

Hello @Daniel-Gruber

Thanks for contacting wolfSSL. The wolfMQTT client sets IO callbacks in wolfSSL, that in turn use the read and write functions defined in mqttnet.c. In this way, the timeout values are used (as long as WOLFMQTT_NO_TIMEOUT is not defined).

Thanks,
Eric Blankenhorn
wolfSSL Support

[mh-ba-dg]

Ok, but that means that only actual transmissions are guarded by the timeout.
The case that mqtt is waiting for an answer of the server, is not guarded by the timeout. And therefore, when the server is never sending an answer, one will receive CONTINUE forever.

Or am I missing something? If the timeout is not meant for that case, a hint somewhere in the documentary would be nice.

But I would prefer if the timeout is guarding the whole publishing process and not just the transmission part :-)

[embhorn]

HI @Daniel-Gruber

I am circling back through older issues... There is a client timeout, such that the client should send a ping request packet to keep the connection alive. If the broker does not respond with a ping response before the command timeout, the connection should be closed.