Replies: 1 comment 5 replies
-
Hi, thanks for your support and use, I'm sorry I'm late in replying. But I have tested the connection and it should not be disconnected because of time.
The error means the other side of the TCP conversation abruptly closed its end of the connection. It is possible that the system shut down the MQTT X process and the MQTT Broker was unable to get the callback information resulting in an active disconnection, or you can check some logs about the server side depending on the time to see the problem. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I tried few times, and for almost the same reasons(client logs) I see disconnect happening after running for few hours. I have tried the option of 'auto reconnect' in the tool which too timed out after retrying for 10 times. Please note that I am running another MQTT client (using another tool) simultaneously and it could connect to the same server and subscribe to same topics and has been running for 2 days. Do you still think I should look into the server side logs? _--------------------------------------------< instance 1>---------------------------------------------------------------- --------------------------------------------< instance 2 >--------------------------------------------------------- |
Beta Was this translation helpful? Give feedback.
-
|
Oh, it does disconnect and reconnect, but it seems weird that I can't reproduce the problem here, and my connection lasts all day. Has your PC ever gone into hibernation during this zone? |
Beta Was this translation helpful? Give feedback.
-
|
No, the PC doesn't hibernate. Power and Sleep Settings are 'Never' to be turned off. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, thanks for your feedback, this might be a BUG and we need to test it more deeply. |
Beta Was this translation helpful? Give feedback.
-
|
Record it on this issue: #1075 |
Beta Was this translation helpful? Give feedback.
-
I have been using MQTTX application for last 4 months. It is very useful tool to connect to my MQTT broker and works as a logger. But the MQTT connection in the tool doesn't last for more than 2 hours. It started successfully with the following messages
[2022-09-16 15:52:34] [INFO] MQTTX client with ID 58c90fdb-eaa7-4f5a-b3e0-d45361e80f11 assigned
[2022-09-16 15:52:34] [INFO] Connect client xxx_demo, MQTT/SSL connection: mqtts://mqtt.myportal.com:8883
[2022-09-16 15:52:34] [INFO] xxx_demo connect success, MQTT.js onConnect trigger
after running for nearly 1.5hrs, it ended with the following error message:
[2022-09-16 17:33:29] [INFO] xxx_demo message arrived: message added "message_63d3c492-b016-4ad1-a60c-04c6a6c2f895" added to topic "server/L00006/pub_sensor_reading", payload: "{"UID":"L00045","OBJ":"32769","TS":"1663320805","SNS":["28.88","-4.88","33.50"]}" MQTT.js onMessageArrived trigger
[2022-09-16 17:33:30] [ERROR] xxx_demo connect fail, MQTT.js onError trigger, Error: read ECONNRESET
at TLSWrap.onStreamRead (internal/stream_base_commons.js:209:20)
[2022-09-16 17:33:30] [INFO] xxx_demo connect close, MQTT.js onClose trigger
Kindly help if there is any setting to prolong the duration of usage.
Beta Was this translation helpful? Give feedback.
All reactions