I have an mqtt client which listens for certain messages, and publishes responses when they're received. Currently when the messages are published, the runloop is then terminated by several errors:
[ERROR mqtt_async_client::client::client] IoTask: Socket disconnected
[ERROR mqtt_async_client::client::client] IoTask: Socket disconnected
[ERROR mqtt_async_client::client::client] IoTask: Socket disconnected
[ERROR mqtt_async_client::client::client] IoTask: Socket disconnected
[ERROR mqtt_async_client::client::client] IoTask: Quitting run loop due to error: channel closed
[ERROR mqtt_async_client::client::client] IoTask: Error connecting: task was cancelled
I previously found that if I didn't specify a large enough buffer, I'd see these errors. But I now see the errors no matter the buffer size.
Is there a way to gain further insight on what I'm doing wrong?
I have an mqtt client which listens for certain messages, and publishes responses when they're received. Currently when the messages are published, the runloop is then terminated by several errors:
I previously found that if I didn't specify a large enough buffer, I'd see these errors. But I now see the errors no matter the buffer size.
Is there a way to gain further insight on what I'm doing wrong?