Is there any chance that the broker didn't like the mqtt connect
message and shutdown the connection and leaving my device alone ...
all during send call?
If the peer disconnects, the socket should be marked disconnected and
the send() should fail with an error.
Is there any chance that the broker didn't like the mqtt connect
message and shutdown the connection and leaving my device alone ...
all during send call?
Em sáb., 26 de jun. de 2021 às 11:42, Flavio Castro Alves Filho
escreveu:
>
> Hello Greg,
>
> No. It was not set :-(
>
> I turned on the confi
Hello Greg,
No. It was not set :-(
I turned on the configuration, but the problem persisted. :-(
Best regards,
Flavio
Em sáb., 26 de jun. de 2021 às 10:41, Gregory Nutt
escreveu:
>
> Do you have CONFIG_NET_TCP_WRITE_BUFFERS=y selected? It is required for
> TCP non-blocking send.
>
--
Flav
Do you have CONFIG_NET_TCP_WRITE_BUFFERS=y selected? It is required for
TCP non-blocking send.
Hello,
I am using the MQTT-C library (https://github.com/LiamBindle/MQTT-C)
in my NuttX project and I am facing a quite interesting issue with a
specific server.
For a specific broker, which is a commercial one, after the connection
is established, when the MQTT Connect message is sent, the firmw
