我对AWS IoT有疑问。我一个月使用相同的代码。但突然间它停止了工作。我在AWS IoT上使用Mqtt over Websocket。
这是我使用的简单代码。
import com.amazonaws.services.iot.client.AWSIotException;
import com.amazonaws.services.iot.client.AWSIotMqttClient;
public class ThingMain {
public static void main(String[] args) {
String clientEndpoint = "endpoint.iot.us-west-2.amazonaws.com";
String clientId = "testing";
AWSIotMqttClient client = new AWSIotMqttClient(clientEndpoint, clientId, "accessKey", "secretKey");
try {
client.connect();
} catch (AWSIotException e) {
e.printStackTrace();
}
}
}
我得到了这个日志:
AVERTISSEMENT: Connect request failure
MqttException (0) - java.io.IOException: WebSocket Response header: Incorrect connection header
at org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:38)
at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:690)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: WebSocket Response header: Incorrect connection header
at org.eclipse.paho.client.mqttv3.internal.websocket.WebSocketHandshake.receiveHandshakeResponse(WebSocketHandshake.java:144)
at org.eclipse.paho.client.mqttv3.internal.websocket.WebSocketHandshake.execute(WebSocketHandshake.java:74)
at org.eclipse.paho.client.mqttv3.internal.websocket.WebSocketSecureNetworkModule.start(WebSocketSecureNetworkModule.java:77)
at org.eclipse.paho.client.mqttv3.internal.ClientComms$ConnectBG.run(ClientComms.java:676)
... 1 more
avr. 04, 2017 11:00:55 PM
com.amazonaws.services.iot.client.core.AwsIotConnection onConnectionFailure
INFOS: Connection temporarily lost
avr. 04, 2017 11:00:55 PM
com.amazonaws.services.iot.client.core.AbstractAwsIotClient onConnectionFailure
INFOS: Client connection lost: leet
avr. 04, 2017 11:00:58 PM
com.amazonaws.services.iot.client.core.AwsIotConnection$1 run
INFOS: Connection is being retried
在这个阶段我不知道出了什么问题。我正在使用这个代码一个月。什么都没有改变,现在它停止了工作。
如果有人可以帮我解决这个问题,那就太棒了。感谢。
答案 0 :(得分:1)
https://github.com/aws/aws-iot-device-sdk-java/issues/23
可能是由于org.eclipse.paho升级v1.1.1
答案 1 :(得分:0)
我也有同样的问题,实际上,如果您在多个区域使用相同的访问密钥和秘密密钥,您将面临此问题。我为每个区域创建了不同的用户。它解决了这个问题。