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
Sounds about right - and I believe I did run into that once or twice
(several eons ago) when I was in a purely java environment.
Interesting it had been set to the CF default - unless it was a newer
server that FRIT setup. Whenever I updated the JVM I pointed CF to a
different directory and the
Yes it's been a while, but I've gotten pulled into database design, and
this group has always been the best place to turn to for technical
knowledge.
The team here inherited a crap database, over 200+ tables for an unexciting
claim system, and is now adding new features. Yes, views are better
I don't think there is anything wrong with using stored procs over inline
SQL to retrieve data. However, in my view of the world this is application
behavior and not reporting. Application behavior should be modeled in
objects and the best way is to use persistent components (Hibernate/ORM.)
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
