timtay-microsoft
commented
5 years ago Here is the simplest repro of the issue that I could make:
String broker = "wss://iot.eclipse.org:443";
String clientId = "JavaSample";
MemoryPersistence persistence = new MemoryPersistence();
try {
MqttClient sampleClient = new MqttClient(broker, clientId, persistence);
sampleClient.setCallback(new MqttCallback()
{
@Override
public void connectionLost(Throwable cause) {
System.out.println("Lost connection");
cause.printStackTrace(); //EOFException thrown here within a few seconds
}
@Override
public void messageArrived(String topic, MqttMessage message) throws Exception {
}
@Override
public void deliveryComplete(IMqttDeliveryToken token) {
}
});
System.out.println("Connecting to broker: "+broker);
sampleClient.connect();
System.out.println("Connected");
} catch(MqttException me) {
me.printStackTrace();
}
while (true)
{
//Just wait for connectionLost callback to happen
}
windbender
siavashsoleymani
OfekRegev
CreateChance
icraggs
JacquesSmuts
ishaansrm
rdasgupt
cristieu9797
SZMOFEI
gitusman
Navaneshwar-Reddy
Please fill out the form below before submitting, thank you!
Upgrading from version 1.2.0 to 1.2.1 appears to introduce a regression on issue #358
Connection appears to be established successfully, but connection is lost shortly afterwards with a stacktrace like
The issue repro's consistently, and affects any WSS connections that I try.
server uri looks like: "wss://mywebsite.net/$iothub/websocket" and the mqtt connection options are all the default values.