Broker times client out while broker is sending client large message.

This page summarizes the projects mentioned and recommended in the original post on /r/MQTT

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • mqtt-cli

    MQTT CLI is a useful command line interface for connecting various MQTT clients supporting MQTT 5.0 and 3.1.1

  • It is correct, the client needs to be sending the PINGRESP if no other control packets are being sent. Perhaps the question here is not the broker but the client. I would suggest testing with a client which is fully conformant with MQTT 3, 3.1.1 and 5.0 specificaation, such as https://github.com/hivemq/mqtt-cli

  • hivemq-community-edition

    HiveMQ CE is a Java-based open source MQTT broker that fully supports MQTT 3.x and MQTT 5. It is the foundation of the HiveMQ Enterprise Connectivity and Messaging Platform

  • It is developed and supported by HiveMQ, so if you observe any issue you can contact the developers directly.

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts