My application source its Datasource settings from a properties file. When I start Tomcat I load the properties file, make changes to it depending on the enviroment Tomcat is running, typically UAT or Production – and base on this pass the appropriate Setting values require for Database connection.
My problem is, when the properties file is updated at bootstrap for the first time with the new connection values, on tomcat – Spring sessionFactory do not seem to acquire the current updated values, and therefore end up with Database connection exception. But when I restart Tomcat – sessionFactory now have access to the updated values.
My question is – do anyone know why sessionFactory only works with the previous values as oppose to the updated settings values?
I Used Maven Filter to replace profile properties at build time.