Also consider simply moving the log4j.xml location to a fixed path and avoid the classpath lookup altogether.
On Wed, Feb 1, 2012 at 10:39 AM, Marvin Addison <[email protected]> wrote: >> Has anyone else come across this issue? >> https://issues.jasig.org/browse/CAS-1094 > > I don't think this is a problem with CAS per se. Based on the stack > trace it looks like this is a difference in classloading behavior, > which is a common cause of problems encountered when deploying CAS on > Weblogic. I'd recommend looking at Weblogic classloading > configuration knobs and see if you can remedy the behavior that way. > > M > > -- > You are currently subscribed to [email protected] as: [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
