I am having an issue where every time I start my apex managed server, it is reading and wiping my config file for apex. This is a problem in that the next boot will cause APEX to totally fail. I have moved my config file to /oracle/apex/apex-config.xml making the required code adjustments inside the war file so it is not stored in the tmp directory. I have an identical copy running on Weblogic 11g and it does not exhibit these behaviors. It seems to be the result of it attempting to encrypt the password and write it back. I am tempted to put a copy of the config file in there with an unencrypted password and make it read only. I am dealing with this now by copying a fresh copy of the file in place in my server start scripts but this is just annoying and insecure. Any thoughts?
THe main difference is I am going from Solaris 10 to RHEL 6 on my operating system.
I am also getting Universal Connection Pool not found in Universal Connection Pool Manager errors every server startup. Can anyone offer any suggestions on how to resolve this as well?
What you are seeing is indeed strange. Did you check WLS log file? May be it will give you some pointers for both issues, the apex-config.xml being overwritten as well as Universal Connection Pool.
Log files are running clean. It appears to be something related to the actual encryption and re-write of the config file. I am not really going to push it that hard as I plan to go to Listener 2.0 and they changed where and how the config are stored there once it is no longer in EA status but what is happening is that the listener configuration file apex-config.xml is being wiped out every time the listener starts and I have to restore it from a backup.