This message was deleted.
# community-support
s
This message was deleted.
m
At least MaxMind's geoiplookup reports all are U.S. based.
e
https://docs.gradle.org/current/userguide/build_environment.html#sec:gradle_configuration_properties
org.gradle.daemon.idletimeout=(# of idle millis)
Gradle Daemon will terminate itself after a specified number of idle milliseconds.
Default is
10800000
(3 hours).
you can turn that down if you want the daemon to stop sooner
it's hard to tell by the IP addresses but I suspect they're maven repositories behind CDNs that have keep-alive
m
Thank you for the info. I may just disable the daemon locally. I will mention that if I was hosting something gradle touched, I would be really pissed to find the entire gradle population stayed connected.
e
Gradle isn't doing anything unusual - it's just using an HTTP connection pool. if the server sends a keep-alive header then the connection stays in the pool.
m
This is like vm versus emacs discussions. I have a different opinion that might not be mainstream. Not going to make a fuss now that I understand the parameters.
I just get nervous when I see open connections to an internal server that is idle. Really nervous.
e
my point is that (regardless of Gradle) it's completely opt-in from the server side whether connections should be left open after each request. why would you be pissed about something that you told all your clients to do