[X] Bug exists Release Version 1.2.5 ( Master Branch)
[X] Bug exists in MQTTv3 Client on Snapshot Version 1.2.6-SNAPSHOT (Develop Branch)
[X] Bug exists in MQTTv5 Client on Snapshot Version 1.2.6-SNAPSHOT (Develop Branch)
Hello,
I am trying to connect my application (which is dockized) with AWS using port 443 using ALPN protocol.
Earlier when I have used JDK8 with Debian 10, there was no issue in the connectivity but recently I have migrated to JDK17 with Debian 12 (due to vulnerability & other requirement), after migration I found application is not able to connect to the MQTT.
When I connect the same application using the port 8883 it does not have any issue.
Please see the below error traces:
FINE 24-07-18 08:26:06.0015 al.TCPNetworkModule start 452 AWSAMVYMSX: connect to host xxxyyy-ats.iot.ap-zone-1.amazonaws.com port 443 timeout 3,000
FINE 24-07-18 08:26:06.0200 ernal.CommsReceiver start 452 AWSAMVYMSX: starting
FINE 24-07-18 08:26:06.0201 ernal.CommsReceiver run 453 AWSAMVYMSX: network read message
FINE 24-07-18 08:26:06.0302 nternal.ClientState get 454 AWSAMVYMSX: wait for new work or for space in the inflight window
FINE 24-07-18 08:26:06.0403 ernal.CommsCallback run 455 AWSAMVYMSX: wait for workAvailable
FINE 24-07-18 08:26:06.0503 nternal.ClientComms internalSend 452 AWSAMVYMSX: 200
FINE 24-07-18 08:26:06.0503 nternal.ClientState send 452 AWSAMVYMSX: pending send key=0 message CONNECT clientId AWSAMVYMSX keepAliveInterval 60
FINE 24-07-18 08:26:06.0503 nal.CommsTokenStore saveToken 452 AWSAMVYMSX: key=Con message=CONNECT clientId AWSAMVYMSX keepAliveInterval 60
FINE 24-07-18 08:26:06.0503 nal.CommsTokenStore saveToken 452 AWSAMVYMSX: key=Con token=org.eclipse.paho.client.mqttv3.MqttToken@59952dc
FINE 24-07-18 08:26:06.0504 nternal.ClientState get 454 AWSAMVYMSX: new work or ping arrived
FINE 24-07-18 08:26:06.0504 nternal.CommsSender run 454 AWSAMVYMSX: network send key=Con msg=CONNECT clientId AWSAMVYMSX keepAliveInterval 60
FINE 24-07-18 08:26:06.0504 nternal.ClientState notifySentBytes 454 AWSAMVYMSX: sent bytes count=14
FINE 24-07-18 08:26:06.0504 nternal.ClientState notifySentBytes 454 AWSAMVYMSX: sent bytes count=12
FINE 24-07-18 08:26:06.0504 re.MqttOutputStream write 454 null: Sent CONNECT clientId AWSAMVYMSX keepAliveInterval 60
FINE 24-07-18 08:26:06.0504 nternal.ClientState notifySent 454 AWSAMVYMSX: key=Con
FINE 24-07-18 08:26:06.0504 ttv3.internal.Token notifySent 454 AWSAMVYMSX: > key=Con
FINE 24-07-18 08:26:06.0504 nternal.ClientState get 454 AWSAMVYMSX: wait for new work or for space in the inflight window
FINE 24-07-18 08:26:06.0559 nternal.ClientState notifyReceivedBytes 453 AWSAMVYMSX: received bytes count=1
FINE 24-07-18 08:26:06.0559 nternal.ClientState notifyReceivedBytes 453 AWSAMVYMSX: received bytes count=84
FINE 24-07-18 08:26:06.0559 ire.MqttInputStream readMqttWireMessage 453 null: received PUBACK msgId 21584
FINE 24-07-18 08:26:06.0559 ernal.CommsReceiver run 453 AWSAMVYMSX: Unknown PubAck, PubComp or PubRec received. Ignoring.
FINE 24-07-18 08:26:06.0559 ernal.CommsReceiver run 453 AWSAMVYMSX: network read message
FINE 24-07-18 08:26:06.0559 nternal.ClientState notifyReceivedBytes 453 AWSAMVYMSX: received bytes count=1
FINE 24-07-18 08:26:06.0559 nternal.ClientState notifyReceivedBytes 453 AWSAMVYMSX: received bytes count=44
FINE 24-07-18 08:26:06.0559 ire.MqttInputStream readMqttWireMessage 453 null: received PUBCOMP msgId 8241
FINE 24-07-18 08:26:06.0559 ernal.CommsReceiver run 453 AWSAMVYMSX: Unknown PubAck, PubComp or PubRec received. Ignoring.
FINE 24-07-18 08:26:06.0559 ernal.CommsReceiver run 453 AWSAMVYMSX: network read message
FINE 24-07-18 08:26:06.0559 nternal.ClientState notifyReceivedBytes 453 AWSAMVYMSX: received bytes count=1
FINE 24-07-18 08:26:06.0559 nternal.ClientState notifyReceivedBytes 453 AWSAMVYMSX: received bytes count=54
FINE 24-07-18 08:26:06.0559 ire.MqttInputStream readMqttWireMessage 453 null: received CONNACK msgId 0 session present:false return code: 56
FINE 24-07-18 08:26:06.0559 nternal.ClientState notifyReceivedAck 453 AWSAMVYMSX: received key=0 message=CONNACK msgId 0 session present:false return code: 56
FINE 24-07-18 08:26:06.0559 ernal.CommsReceiver run 453 AWSAMVYMSX: Stopping, MQttException
Throwable occurred: MqttException (56)
at org.eclipse.paho.client.mqttv3.internal.ExceptionHelper.createMqttException(ExceptionHelper.java:31)
at org.eclipse.paho.client.mqttv3.internal.ClientState.notifyReceivedAck(ClientState.java:1053)
at org.eclipse.paho.client.mqttv3.internal.CommsReceiver.run(CommsReceiver.java:151)
at java.base/java.lang.Thread.run(Thread.java:840)
Hello,
I am trying to connect my application (which is dockized) with AWS using port 443 using ALPN protocol.
Earlier when I have used JDK8 with Debian 10, there was no issue in the connectivity but recently I have migrated to JDK17 with Debian 12 (due to vulnerability & other requirement), after migration I found application is not able to connect to the MQTT.
When I connect the same application using the port 8883 it does not have any issue.
Please see the below error traces:
Could you suggest what can be wrong here?