You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Observed Assert in MQTT Application,
once ConnectivityMQTTMqtt succeeded , the try to publish the data to broker , On Subscribe side not received any data and observed asserted at Filename 3rd-party/ServalStack/src/Msg/TcpMsg.c , line no 91 in a few minute.
The text was updated successfully, but these errors were encountered:
For me MQTT is quite stable. I can only reproduce your error by manually disconnecting the XDK from the MQTT server, i.e. by killing the server. From what I can tell this assert in TcpMsg.c:91 arrises from the builtin MQTT message handler, which tries to get a message from an invalid socket. I would therefore classify this as a bug in the XDK's SDK and not primarily in Mita code generation.
If you have further information that clarifies your issue/contradicts my investigation feel free to reply.
Observed Assert in MQTT Application,
once ConnectivityMQTTMqtt succeeded , the try to publish the data to broker , On Subscribe side not received any data and observed asserted at Filename 3rd-party/ServalStack/src/Msg/TcpMsg.c , line no 91 in a few minute.
The text was updated successfully, but these errors were encountered: