I think Daniel may have had a fix for this one, but based on what you are reporting, it likely needs to be investigated further. Go ahead and submit an issue plz.
From: [email protected] [mailto:[email protected]] On Behalf Of Travis Schmidt Sent: Wednesday, March 9, 2016 4:18 PM To: [email protected] Subject: [cas-user] Log4j configuration bug introduced for Tomcat in 4.2.0-RC3 We have been trying to upgrade our project from 4.2.0-RC2 to RC3 and also run the app on Tomcat. With changes included in RC3 for CasLoggerContextIniitializer, we are no longer able to pull log4j configuration from a location other then the default which is "classpath:log4j2.xml". Any path we set in cas.properties seems to be ignored. We verified this behavior by setting up a clean maven overlay without any of our code, setting up cas.properties and log4j2.xml in /etc/cas. Switching the pom.xml cas.version between RC2 and RC3 then is all that is need to see this happen. Travis -- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <mailto:[email protected]> . Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/. -- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/.
