MQTT connect issue when sending automatic post connection message

DEV TMS MQTT
1

Hi
I get a strange issue when connection is started, connection is established then close with an exception
On same environment to same MQTT Server, MQTTX connection works fine
Server = MQTT from Scaleway type 3.1.1

It seems just after sending the first message socket is closed (by server ?)

LogEx >> CLIENT- Connecting ---------------------------
LogEx >> CLIENT- Handling Outgoing Packet ---------------------------
LogEx >> CLIENT- Sending packet to CommThread ---------------------------
LogEx >> CLIENT- Packet added to queue ---------------------------
LogEx >> Comm thread - Started
LogEx >> Keep Alive thread - Started
LogEx >> Initializing Indy TCP Client
LogEx >> Connecting Indy TCP Client
LogEx >> Socket allocated ...
LogEx >> TIdIOHandlerStack - resolving...
LogEx >> TIdIOHandlerStack - connecting...
LogEx >> TIdTCPClient - connected...
LogEx >> TCP connection established.
LogEx >> Comm thread - Packet: 0 Type:CONNECT Qos:0 - SENDING --- 00010000 01000000 00000000 00000100 01001101 01010001 01010100 01010100 00000100 01001010 00000000 01111000 00000000 00001110 01101101 01110001 01110100 01110100 01111000 01011111 00110110 01100101 01100100 01000100 00110111 00110001 00110011 01100101 00000000 00100100 01100100 00110110 00110010 00110011 00110011 01100110 01100010 00110111 00101101 00110111 00110000 01100011 01100110 00101101 00110100 00110000 00110010 01100011 00101101 00111000 01100011
LogEx >> TIdIOHandlerStack - disconnected. Déconnecté.
LogEx >> Exception reading data from the socket.
LogEx- Exception >> La connexion s'est fermée proprement.

What is the role of this send after established connection ?
Binary conversion with Binary to Text Converter

image
image831×459 13.2 KB

It seems the content includes

  • Cliend_ID = mqttx_6edD713e
  • partial part of the Device ID as username (I need with this server to communicate Device ID into the username) the device ID is like d6233fb7-70cf-402c-8c9d-562a1cXXXXXX (for test purpose) so it appears shortened.

Thanks for help

Sylvain

2

Not sure what might be causing this. Did you try with a different broker? Is this also happening on a different machine? Is this the latest version of TMS MQTT?
If a problem persists, can you send a sample source project + steps with which we can reproduce the issue here so we can investigate.

3

Hi Bruno
Test project sent in PM

Thanks

Sylvain

4

We will check it