-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Connection is stuck after multiple calls 'publish' and sending a large (±200kb) WebSocket message in Chrome #1775
Comments
a1leks
changed the title
Connection is stuck after multiple calls 'publish' and sending a large (±200kb) WebSocket message.
Connection is stuck after multiple calls 'publish' and sending a large (±200kb) WebSocket message in Chrome
Jan 11, 2024
I suggest you to give a look at: Lines 262 to 285 in c8b6695
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello there! First of all, thank you for the library. I appreciate your work.
I faced a strange issue in Chrome 120. My MQTT.js version is 5.3.4, QoS is 1, the broker is custom-made.
My WebSocket MQTT connection stops working after sending numerous packets in a single 200KB WS request in Chrome. The connection seems fine, and there are no errors. However, the server stops responding after receiving a large message. This issue is specific to Chrome; it works well in Firefox and Safari.
More details:
I call client.publish 500-1000 times synchronously in a loop to send numerous small buffered messages.
I see that WS send it in a one big message. It looks like:
The broker correctly handles approximately half of the messages from this WS request and then it's just stuck. Then I can publish new messages, but they are not received/processed by the broker and I don't get a PUBACK message
This might be a broker issue or even a Chrome issue; however, I have several questions about MQTT.js and hope the answers will be useful not only for me.
Thanks!
The text was updated successfully, but these errors were encountered: