does this ever vTaskDelay? about esp-mqtt HOT 4 CLOSED

It does. The mutex locks and unlocks, and selects on the socket will yield to other tasks until data is available or the mutexes are accessible. I never ran into issues with the watchdog until now.

Is it possible that your connection is very unstable? The errors -13 (pong timeout) and -4 (network timeout) suggest that the client waited a long time for data that didn't arrive in time.

from esp-mqtt.

it's strange; subscribing takes seconds most times. But the server (mosquitto) logs indicate immediate response. The esp was about 3m from the switch.
Subsequent to the above, I do have disconnects. I think it's an interaction between different threads (tasks) in esp. As soon as I enabled many subscriptions again (5), it started failing. I'd disabled a lot of the functionality to diagnose.... the app can have MANY subscriptions (40+).
I put some external protection around MQTT activity as well as your mutexes, and it still showed issues.

have to say, this is my first esp32 try, so learning all the time.
App is https://github.com/btsimonh/esp32-ble2mqtt/tree/btsimonh-platformio2
it involves BLE, so I'm on esp-edf 3.1.1 (in theory), and the BLE/wifi interaction could be an issue. Seems we're on bleeding edge with esp32 and BLE.

ref your reply;
when subscribing, it calls ***_until with available=0
Are you SURE that this will not tight loop until a packet comes in?

from esp-mqtt.

I suspect these issues are caused by another component in your project.

The call to lwmqtt_cycle_until caused by a subscribe will block as the underyling read operation will block.

from esp-mqtt.

I will close this for now, please reopen if there is still an issue.

from esp-mqtt.