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
Deadlock when sending message inside ApplicationMessageReceivedHandler #731
Comments
I guess that the |
Which issue? This one #158? |
No, I wasn't referring to that issue. I meant that when @chkr1011 wrote that test, he probably added the |
Ah, okay. Yeah, it might be like that. |
it may be a duplicate of #648 |
This seems to be very similar, yes. |
OK, so I'm closing the issue. Thanks |
Just for reference again: Check out @chkr1011's comments under #648 (comment) and #648 (comment) to find workarounds. |
Describe the bug
If I try to publish a message with AtLeastOnce QoS from the ApplicationMessageReceivedHandler, the message is correctly sent, but the execution of the handler is stuck. It looks like a deadlock.
Everything is working fine with AtMostOnce QoS
Which project is your bug related to?
Client
To Reproduce
I changed a test so that it fails, showing the issue: paolofulgoni@d351a72
Expected behavior
I expect the handler to continue the execution.
The text was updated successfully, but these errors were encountered: