-
Notifications
You must be signed in to change notification settings - Fork 233
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
feat(iot-dev): Add configurable message expiration check job #1762
Conversation
Previously, the client would only check for expired messages each time it tried to send a message. Now it will check for expired messages even if the client is idle.
{ | ||
try | ||
{ | ||
correlationCallbackCleanupThread.start(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We shouldn't start/stop this thread when one device in a multiplexed connection is lost. Only start/stop it when the whole connection is opened/closed
* | ||
* @return true if the packet has been in the queues for longer than the device operation timeout and false otherwise | ||
*/ | ||
private boolean hasOperationTimedOut(long startTime, String deviceId) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unused method
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
Previously, the client would only check for expired messages each time it tried to send a message. Now it will check for expired messages even if the client is idle.