Skip to content

Assume publish response as ping response#128

Open
cosmo0920 wants to merge 1 commit intonjh:mainfrom
cosmo0920:assume-publish-response-as-pingresp
Open

Assume publish response as ping response#128
cosmo0920 wants to merge 1 commit intonjh:mainfrom
cosmo0920:assume-publish-response-as-pingresp

Conversation

@cosmo0920
Copy link
Copy Markdown

Fixes #127
This option should be needed due to high frequently traffic environment.

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

Signed-off-by: Hiroshi Hatake cosmo0920.oucc@gmail.com

This option should be needed due to high frequently traffic environment.

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

Signed-off-by: Hiroshi Hatake <cosmo0920.oucc@gmail.com>
@phlegx
Copy link
Copy Markdown

phlegx commented Sep 5, 2023

Cool! Exactly my case. Thx!

phlegx added a commit to phlegx/ruby-mqtt that referenced this pull request Sep 5, 2023
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.

MQTT client on weak CPU and high traffic environment

2 participants