Skip to content

fix(iot-dev): Fix issue where notfiy call was not wrapped by synchronization block#893

Merged
timtay-microsoft merged 2 commits intomasterfrom
timtay/notifyFix
Aug 13, 2020
Merged

fix(iot-dev): Fix issue where notfiy call was not wrapped by synchronization block#893
timtay-microsoft merged 2 commits intomasterfrom
timtay/notifyFix

Conversation

@timtay-microsoft
Copy link
Copy Markdown
Member

All notify calls must be wrapped in synchronization blocks on the object that will be notified. Otherwise the notify call will throw an IllegalMonitorStateException and won't wake up the send thread as expected.

This PR just adds that synchronization block so that when the message is requeued, it will wake up the send thread

…ization block

All notify calls must be wrapped in synchronization blocks on the object that will be notified. Otherwise the notify call will throw an IllegalMonitorStateException and won't wake up the send thread as expected
Copy link
Copy Markdown
Contributor

@bikamani bikamani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 Wondering how this got missed!!

@timtay-microsoft
Copy link
Copy Markdown
Member Author

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 4 pipeline(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants