From ba2acbf173837c659dfd1f72a0bb9c4430679541 Mon Sep 17 00:00:00 2001 From: Isamu Tanaka Date: Thu, 7 Dec 2017 11:03:16 +0900 Subject: [PATCH] AWS IoT now requires clientId AWS IoT worked with this module before but it now requires clientId. To make it enable, my change is: MqttConnector.java // clientId = "MxClient_" + xasId + "_" + hostname + "_" + brokerHost + "_" + brokerPort; clientId = "bluemix-receiver"; This solution is just temporal. It is much better to accept clientId for setting from Mendix widget. --- javasource/mqttclient/impl/MqttConnector.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/javasource/mqttclient/impl/MqttConnector.java b/javasource/mqttclient/impl/MqttConnector.java index b4f812e..b407237 100644 --- a/javasource/mqttclient/impl/MqttConnector.java +++ b/javasource/mqttclient/impl/MqttConnector.java @@ -95,7 +95,7 @@ public MqttConnection(ILogNode logger, String brokerHost, Long brokerPort, Stri clientId = "a:" + brokerOrganisation + ":" + xasId; }else{ broker = String.format("tcp://%s:%d", brokerHost, brokerPort); - clientId = "MxClient_" + xasId + "_" + hostname + "_" + brokerHost + "_" + brokerPort; + clientId = "bluemix-receiver"; } logger.info("new MqttConnection client id " + clientId);