the config files (except for the log4j.properties) the appserver reads at startup are cached at startup, so you need to restart the appserver to pickup the changes.
why is the AD server in the environment changing so much ? that seems bad...
Thanks for the confirmation, Bill. I suspected as much, but wanted confirmation.
There's a big DC migration project going on at the moment, so everything is in somewhat of a state of flux. It should start to settle down over time, but we want to be a little more proactive in keeping things alive!
In 8.5 we updated to java 7 which fixes the old defect of java not honoring the kdc_timeout setting so it can roll to the next KDC in the list. not sure if that will help ☺