-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Command acknowledgement deadlock inside the publish loop #11
Comments
nik-markovic
changed the title
Command acknowledgement deadlock inside a publish loop
Command acknowledgement deadlock inside the publish loop
Sep 17, 2021
nik-markovic
pushed a commit
that referenced
this issue
Sep 23, 2021
nik-markovic
pushed a commit
that referenced
this issue
Sep 28, 2021
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When command is received while telemetry is being published, this deadlock could occur:
Somewhere this ends up releasing with message "get_event_payload: EAGAIN", but only after a long time.
I am also concerned about calling iotc_nrf_mqtt_loop() inside iotc_nrf_mqtt_publish(). We may end up using up too much stack because this could also result in an inbound mqtt message from broker. iotc_nrf_mqtt_loop() should probably only be called from main to be able to better estimate stack usage. This could maybe even cause recursion. I am not sure how much of an impact this change would have on MQTT confirmation code.
@syjen Assigning to you, but feel free to reassign this ticket to someone else on your team.
The text was updated successfully, but these errors were encountered: