4 ms·
It doesn’t help that Java’s default configuration is to cache DNS entries forever for “security”[0]. Any long running server that makes external requests will e
by jonhohle 4y ago
It doesn’t help that Java’s default configuration is to cache DNS entries forever for “security”[0]. Any long running server that makes external requests will eventually hit an issue where one their dependencies no longer works because DNS has changed and the TTL is ignored. I’ve seen this bite teams for 15 years and it will probably keep doing so well into the future.
0 - https://docs.oracle.com/javase/7/docs/technotes/guides/net/properties.html https://docs.oracle.com/javase/7/docs/technotes/guides/net/p...
- pionar 4y ago.NET HTTP clients used to suffer from this, too, but they no longer do as of .Net Core 3, as long as they're used correctly.
- nikanj 4y agoOnly if you have a security manager enabled (=are running in an applet/webstart). The entire security manager concept has been deprecated, so things are looking better
- russellendicott 4y agoI seem to recall that HAProxy and Squid used to do this too.