Close received after close

[vCloudSail]

Why is this error always reported when running for a long time: WebSocket connection to 'ws://xxx/mqtt' failed: Close received after close

version: 4.2.8
browser: Microsoft Edge 95.0.1020.53

[YoDaMa]

Great question. I dunno. Close received after a close suggests that the websocket connection was closed and then subsequently there was a call to close that same websocket connection despite it already being closed. Can you repro it repeatably?

[H2pl4U]

I encountered the same problem, I need to close the socket when reconnecting, but how to configure the code?

[vCloudSail]

Great question. I dunno. Close received after a close suggests that the websocket connection was closed and then subsequently there was a call to close that same websocket connection despite it already being closed. Can you repro it repeatably?

I can't manually reproduce this situation, which typically occurs multiple times after MQTTJS has been running for a long time

[vCloudSail]

I encountered the same problem, I need to close the socket when reconnecting, but how to configure the code?

I have changed to the paho.mqtt.js library

[amnonbb]

It's happen when you leave tab inactive for duration more than ~ 1 minutes

[vCloudSail]

It's happen when you leave tab inactive for duration more than ~ 1 minutes

Do you mean web sleep is the cause?

[amnonbb]

Sorry, din not understand.
Actually yes, looks like it's cause by web sleep.

[YoDaMa]

@amnonbb can you provide a reproducible code snippet please. will attempt repro and debug.

[amnonbb]

I discovered that if i connect with keepalive option = 1 or 2 sec, the error above fire after ~ 5 seconds on inactive tab

[YoDaMa]

@amnonbb and you're just starting a client, connecting via WS, and sending messages? do you have a code snippet i can paste and run?

[amnonbb]

https://mqtt-js.kab.sh

[YoDaMa]

thanks!

[shuiRong]

same here.

[Zc0412]

I have the same problem

[jingyuLin1999]

same here

[jingyuLin1999]

Has been troubled by this issue. come on!

[wtto00]

When you are listening for a message event, then execute client.end() to close the connection.

If you receive another message during the closing process, it will trigger a Close received after close error.

Change to client.end(true). It will be OK.

[robertsLando]

MQTT 5.0.0 BETA is now available! Try it out and give us feedback: npm i mqtt@beta. It may fix your issues

[robertsLando]

This could be related to #1257 and may be fixed in latest version. Could someone check this?

[amnonbb]

https://mqtt-js.kab.sh

This still alive. Update to v5.0.1

[LiuZiqi-dual]

This could be related to #1257 and may be fixed in latest version. Could someone check this?

npoe, the problem still exists, it's due to the browser tab throttling, and it's not uncommon for setInterval and setTimeout to lose precision in certain situations (e.g. when a tab is inactive)

The solution I can think of is to create highly accurate timers via Web Wroker (since Web Workers run in a thread separate from the main thread, they are not affected by the main thread and can accurately trigger timer events at any time, even when the main thread's event loop is blocked or the browser tab is inactive).

Of course this comes at the expense of mqtt's compatibility, making it unsupported in Internet Explorer 9 and below.

[Nakus0426]

This issue still occurs in version 5.0.3

[robertsLando]

May be related to #1257

[robertsLando]

May get fixed by #1753 , available starting from version 5.3.2

[binzhou1986]

When you are listening for a message event, then execute client.end() to close the connection.

If you receive another message during the closing process, it will trigger a Close received after close error.

Change to client.end(true). It will be OK.

great ! MqttClient.prototype.end = function () {...} use end(ture) is very useful