If the first UDP response can be back in a second then there is no extra
workload. This should be the most common case since Kerberos is usually used in
an enterprise environment with a high network speed. In most cases, the re-sent
of a request is due to failed KDCs or even false settings which
Missed the security-dev list.
On 7/7/2014 10:39 AM, Xuelei Fan wrote:
> I have not read the fix. I was just wondering that this fix save the
> wait time, but increase the networking traffics, and increase the
> workload of KDC servers. I think the KDC timeout should be corner cases
> for TCP, an
I have not read the fix. I was just wondering that this fix save the
wait time, but increase the networking traffics, and increase the
workload of KDC servers. I think the KDC timeout should be corner cases
for TCP, and it is tolerable for UDP connections. I'm not confident
that this is a cost-e
Hi All
Please review the code change at
http://cr.openjdk.java.net/~weijun/8014870/webrev.00/
In Kerberos, when trying to request for a ticket, we tried multiple KDC servers
for multiple times. Before this fix, we connect to a server, wait for 30
seconds (the default kdc_timeout). If there
