Glad to hear you find things resolved, Brooks. But to be clear, the resources I pointed to did clarify that this was a JVM issue (I just didn't say that specifically in my pointing them out). :-)
They did also talk about changing the TTL value. Finally, they did also propose that just restarting the instance could have helped. Just sharing in case your "change" comes back some day to still seem not to work. It may be that simply restarting CF (and therefore the JVM) would be the most expedient solution. Saying that as much for other readers who may someday find/reuse this thread, too. /charlie From: ad...@acfug.org [mailto:ad...@acfug.org] On Behalf Of Wilson, Brooks Sent: Tuesday, May 21, 2013 9:25 AM To: discussion@acfug.org Subject: RE: [ACFUG Discuss] Getting Connection Refused Greetings: It turns out that technically speaking CF doesn't cache the DNS, but the JVM does. In this case the JVM DNS cache was corrupted and we were being directed to the wrong ip. We set the time to live parameter in the JVM DNS cache to something other than "forever" and restarted the server. This fixed the problem. This one was very interesting and challenging. Sincerely, Brooks ------------------------------------------------------------- To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by http://www.fusionlink.com -------------------------------------------------------------
