Auto Reconnect time now maxes out at 128 seconds

As suggested by @mingdong & @lucaslafarga in PR #210, the Automatic reconnect timer could never reach the max of 120 because of the accidental != check, setting the check to < 128000 now means that the reconnect delay will max out at 128 seconds correctly.

Author: jpwsutton

org.eclipse.paho.client.mqttv3/src/main/java/org/eclipse/paho/client/mqttv3/MqttAsyncClient.java

@@ -1064,7 +1064,7 @@ public void reconnect() throws MqttException {
 	 * Attempts to reconnect the client to the server.
 	 * If successful it will make sure that there are no further
 	 * reconnects scheduled. However if the connect fails, the delay will double
-	 * up to 2 minutes and will re-schedule the reconnect for after the delay.
+	 * up to 128 seconds and will re-schedule the reconnect for after the delay.
 	 * 
 	 * Any thrown exceptions are logged but not acted upon as it is assumed that 
 	 * they are being thrown due to the server being offline and so reconnect
@@ -1087,7 +1087,7 @@ public void onSuccess(IMqttToken asyncActionToken) {
 				public void onFailure(IMqttToken asyncActionToken, Throwable exception) {
 					//@Trace 502=Automatic Reconnect failed, rescheduling: {0}
 					log.fine(CLASS_NAME, methodName, "502", new Object[]{asyncActionToken.getClient().getClientId()});
-					if(reconnectDelay != 120000){
+					if(reconnectDelay < 128000){
 						reconnectDelay = reconnectDelay * 2;
 					}
 					rescheduleReconnectCycle(reconnectDelay);