refactor(nacos-client): 修改与本pr无关的注释信息
This commit is contained in:
parent
456e84785f
commit
ecc015402e
@ -344,8 +344,6 @@ public class ClientWorker {
|
||||
|
||||
List<String> params = Arrays.asList(Constants.PROBE_MODIFY_REQUEST, probeUpdateString);
|
||||
|
||||
// Take a custom timeout parameter to circumvent network errors caused by network latency
|
||||
|
||||
List<String> headers = new ArrayList<String>(2);
|
||||
headers.add("Long-Pulling-Timeout");
|
||||
headers.add("" + timeout);
|
||||
@ -560,6 +558,6 @@ public class ClientWorker {
|
||||
ConfigFilterChainManager configFilterChainManager;
|
||||
private boolean isHealthServer = true;
|
||||
private long timeout;
|
||||
private volatile double currentLongingTaskCount = 0;
|
||||
private double currentLongingTaskCount = 0;
|
||||
private int taskPenaltyTime;
|
||||
}
|
||||
|
@ -241,7 +241,6 @@ public class LongPollingService extends AbstractEventListener {
|
||||
// AsyncContext.setTimeout()的超时时间不准,所以只能自己控制
|
||||
asyncContext.setTimeout(0L);
|
||||
|
||||
// I think there is a problem with the task delay setting here that could easily cause a client read timeout
|
||||
scheduler.execute(
|
||||
new ClientLongPolling(asyncContext, clientMd5Map, ip, probeRequestSize, timeout, appName, tag));
|
||||
}
|
||||
|
Loading…
Reference in New Issue
Block a user