Closed ashdam closed 3 months ago
Hi @ashdam,
ERR_QUEUE_SIZE error means that MQTT client was not able to deliver all messages to the platform. It is a result of not sent messages to the platform, because platform disconnects the gateway. Before ThingsBoard 3.7.0 - it often returns 7 reason code and closes connection due to different reasons. The most often reason that we experienced with this error is exceeding transport rate limits for device or tenant. To get information why TB disconnects the gateway you can check logs. I think this can be also checked on TB Edge.
I'm also experiencing this problem I get this error after a while after docking a large number of devices using modbus. Using the code from the end of July works fine
This related with a performance issue we currently have. Closing....
Describe the bug
IotGateway lost connection with TB Edge PE after a restart on iotgateway, after 8 hours memory gets full, restarted edge with new parameters (increased MQTT new message size limit ) but never recovers to a normal status
Steps followed: 1) Loaded a big connector OPCUA asyncua with 1000 variables 2) lost syncronizacion with TB Edge PE 3) Waited 7-8 hours Iotgateway claiming memory full (in memory config) 4) TB Edge PE: 4.1 - Shows error on MQTT size 4.2 Increased NETTY_MAX_PAYLOAD_SIZE env variable and restarted 4.3 - Recovers 5) IotGateway does not recover and keep through memory full error 6) IoTGateway restarted and went ok.
Our concern is about the recovery we found many situations were communication/syncronization is not recovered and GW keeps on throwing ERRORs
Connector name (If bug in the some connector): OPC-UA asyncua Connector
Error traceback (Gateway):
Versions (please complete the following information):