Bug #9640
port range resiliency issue
0%
History
#2 Updated by Greg Shah over 1 year ago
In #9533-19, a customer had a server configured with admin port 7443 but a web client port range of 7403 - 7470 which certainly cannot work well. They reported that it was not just a small effect. The entire system ground to a halt.
They retested after fixing the configuration problem and the testing went better. We don't have a sure answer that the port conflict caused the really bad results but it seems likely.
I suspect that our approach of using scanning for detecting the open ports is making us very fragile in this case. If that is correct, even a single port that responds in an unusual way can potentially cause a denial of service. That would not be OK for us to allow.
Please see if we can duplicate this bad behavior and if so we need to resolve it.
#3 Updated by Sergey Ivanovskiy over 1 year ago
- Status changed from New to WIP