topic Re: Setting clientID in MQTT-Connector? in ArcGIS GeoEvent Server Questions

Setting clientID in MQTT-Connector?

TimLeefmann — Tue, 16 Feb 2021 09:58:07 GMT

We run a verneMQ broker that I want to connect to with the MQTT Input Connector. However, I can't establish a succesful connection.

Here the error message from the log:

Unexpected error during MQTT receiver initialization. org.eclipse.paho.client.mqttv3.MqttSecurityException: Bad user name or password at org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:28) ~[?:?] at org.eclipse.paho.client.mqttv3.internal.ClientState.notifyReceivedAck(ClientState.java:1040) ~[?:?] at org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:151) ~[?:?] at java.lang.Thread.run(Thread.java:748) [?:?]

I succesfully tested the connection from the Geoevent Server using MQTT explorer with the same credentials, except for adding a clientID. The connector itself was similarly succesfully tested using "test.mosquitto.org" as a broker. Therefore I assume, the unsuccesful login may be caused by the missing clientID. Is there an option available that would allow me to supply a clientID using the Geovent MQTT Connector?

Re: Setting clientID in MQTT-Connector?

brudo — Tue, 16 Feb 2021 18:30:33 GMT

I did some experimental changes in a local branch a few years ago, that I didn't ever publish to GitHub or submit as a pull request, as the project it was needed for did not materialize. Among other things, it added a property predefClientId, along with several other properties that define behavior on disconnect / reconnect. I'm not sure what state it was in when I left off, but I'll look it over and see about publishing it to my fork.

Re: Setting clientID in MQTT-Connector?

TimLeefmann — Wed, 17 Feb 2021 15:15:32 GMT

Would be great if you could share it. And good to know that this option is not included in the current connector.

Re: Setting clientID in MQTT-Connector?

TimLeefmann — Wed, 17 Feb 2021 21:32:33 GMT

Thanks for your help. As you suggested I added a property to the transporter for defining the ClientD (instead of generating one) and managed to succesfully receive a message from our mqtt broker.