Skip to content
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.

Sign up for GitHub

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

Jump to bottom

MQTT client on weak CPU and high traffic environment #127

Open
cosmo0920 opened this issue Dec 9, 2020 · 0 comments · May be fixed by #128
Open

MQTT client on weak CPU and high traffic environment #127

cosmo0920 opened this issue Dec 9, 2020 · 0 comments · May be fixed by #128

Comments

@cosmo0920
Copy link

cosmo0920 commented Dec 9, 2020 •
edited

When flood of messages are reached in this client on weak CPU environment,
keep_alive! response may not reached until response timeout and
causes MQTT::ProtocolException with "No Ping Response received for
xxx seconds":

Protocol error occurs in in_mqtt.,MQTT::ProtocolException,No Ping Response received for 23 seconds
/media/Data2/Gitrepo/ruby-mqtt/lib/mqtt/client.rb:541:in `keep_alive!'
/media/Data2/Gitrepo/ruby-mqtt/lib/mqtt/client.rb:474:in `receive_packet'
/media/Data2/Gitrepo/ruby-mqtt/lib/mqtt/client.rb:272:in `block in connect'
@cosmo0920 cosmo0920 linked a pull request Dec 9, 2020 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Assume publish response as ping response cosmo0920/ruby-mqtt
1 participant
@cosmo0920