tree 601252cbcbf2f10aceeae1729c9dd033e53a0469
parent 9d864c224e0943cf1cba95ec3f967211edc4f0cb
author xiaolong ran <rxl@apache.org> 1626076158 +0800
committer GitHub <noreply@github.com> 1626076158 +0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJg6/P+CRBK7hj4Ov3rIwAA1swIAHlQCjwfZ46XlET/wPaPit4G
 HZs/gTI1gryw3NctNRHlRnwRJezrDyc2iRts2qu645ZJWiozm7NuPyWXEYyLDMBv
 IUzVnYkj4O9/rVe8UGSembXgj5rY65OLYQWvBX2KP3Ls2x+4y/ac8WnlKXr9leqL
 nS8VzG289ziPMSaFZSO6MevjoRpbyODkxkF5i5UAw8Djg+8iQhGbl8Wa+BOYI05m
 gpMekLoJzZqUJIcuOz2is8BqzoE9tM7rqVOLFEUjRNmnhZ8VTVxyCPVkbj2x0nxZ
 +2CJGW3dWO0Q1e5CActyRAcEgYUnfUI5dzo2+xXe40O3ccLBSynPe+xzUp8AaOI=
 =+vis
 -----END PGP SIGNATURE-----
 

Fix default connection timeout (#563)

Signed-off-by: xiaolongran <xiaolongran@tencent.com>


### Motivation

In Java SDK, the default connection timeout is **10** sec

```
private int connectionTimeoutMs = 10000;
```

The problem here is that when the load of the broker is high, there is no way to complete the processing and creation of the connection within 5s, which will cause the client to constantly create new connections and try to establish a connection with the broker, and the broker Continuously disconnecting from the client, forming a vicious circle

### Modifications

Replace 5 sec of connection timeout with `10` sec